My Vaadin+Spring Boot App suddenly stops starting locally. I already purged IntelliJ Caches, rebuilt the project and made a mvn clean. Does anyone can help me find the issue? At the following point the log stops logging, but wont finishing frontend compiling. the App is also not reachable in the browser at this point
------------------ Starting Frontend compilation. ------------------
2021-12-21 21:07:47.371 INFO 4376 --- [onPool-worker-3] dev-webpack : Running webpack to compile frontend resources. This may take a moment, please stand by...
2021-12-21 21:07:49.753 INFO 4376 --- [onPool-worker-3] dev-webpack : Started webpack-dev-server. Time: 2383ms
Related
I am trying to learn Vaadin with spring boot but when ever I compile the code,its always showing erro when frontend part start the compilation
------------------ Starting Frontend compilation. ------------------
2022-06-12 21:50:58.951 INFO 9764 --- [nPool-worker-19] c.v.b.devserver.AbstractDevServerRunner : Running Webpack to compile frontend resources. This may take a moment, please stand by...
2022-06-12 21:50:58.965 INFO 9764 --- [v-server-output] c.v.b.devserver.DevServerOutputTracker : /usr/bin/node: --openssl-legacy-provider is not allowed in NODE_OPTIONS
------------------ Frontend compilation failed. ------------------
I am running node v16.15 and jdk 17
Facing this problem when i use linux base system but not happening on window with the same node version
Tried to use unset NODE_OPTIONS but not working
Any suggestion please
It is an issue with openssl3 see issue https://github.com/vaadin/flow/issues/13889
It should probably be fixed in node 16.16
I followed exact same step as per [1] and when I execute
./gradlew tomcatRunWar
Process didn't work after 92%
16:14:48.912 [localhost-startStop-1] INFO o.s.j.c.CachingConnectionFactory - Established shared JMS Connection: ActiveMQConnection {id=ID:Gayans-MacBook-Pro.local-58639-1559299488784-1:1,clientId=null,started=false}
16:14:48.971 [localhost-startStop-1] INFO o.a.f.i.c.b.WarWebApplicationInitializer - Started WarWebApplicationInitializer in 58.585 seconds (JVM running for 141.561)
The following warnings have been detected with resource and/or provider classes:
WARNING: A HTTP GET method, public java.lang.String org.apache.fineract.portfolio.self.savings.api.SelfSavingsApiResource.template(java.lang.Long,java.lang.Long,java.lang.String,javax.ws.rs.core.UriInfo), should not consume any entity.
Started Tomcat Server
The Server is running at http://localhost:8080/fineract-provider
Building 92% > :tomcatRunWar
[1] https://github.com/apache/fineract
./gradlew tomcatRunWar is actually a way to run the Fineract App in Dev mode. The logs you pasted shows Fineract is actually doing the right thing by starting up in Dev mode. What you can do now is get the web app here: https://github.com/openMF/community-app, build it using the instructions in the read me and try to login to the Fineract backend using username: mifos, password: password
I'm running Mac OS. I've set up the Payara server with NetBeans. And when I'll try to run the server it never shows the green 'dot' that indicates its online status, instead it shows the 'loading' dot forever.
However, I can access it on http://localhost:4848, but when I try to deploy an application to the server I get this error:
GlassFish Server is running.
Starting GlassFish Server
Initial deploying slit-ee to /Users/christian/slit/slit-ee/dist/gfdeploy/slit-ee
Completed initial distribution of slit-ee
GlassFish Server, deploy, null, false
/Users/christian/slit/slit-ee/nbproject/build-impl.xml:307: The module has not been deployed.
See the server log for details.
BUILD FAILED (total time: 22 seconds)
And the full server log
objc[1865]: Class JavaLaunchHelper is implemented in both /Library/Java/JavaVirtualMachines/jdk1.8.0_111.jdk/Contents/Home/bin/java (0x105e334c0) and /Library/Java/JavaVirtualMachines/jdk1.8.0_111.jdk/Contents/Home/jre/lib/libinstrument.dylib (0x105efb4e0). One of the two will be used. Which one is undefined.
Launching GlassFish on Felix platform
nov 28, 2016 2:14:21 AM com.sun.enterprise.glassfish.bootstrap.osgi.BundleProvisioner createBundleProvisioner
INFO: Create bundle provisioner class = class com.sun.enterprise.glassfish.bootstrap.osgi.BundleProvisioner.
Registered com.sun.enterprise.glassfish.bootstrap.osgi.EmbeddedOSGiGlassFishRuntime#18808234 in service registry.
#!## LogManagerService.postConstruct : rootFolder=/Users/christian/opt/payara41/glassfish
#!## LogManagerService.postConstruct : templateDir=/Users/christian/opt/payara41/glassfish/lib/templates
#!## LogManagerService.postConstruct : src=/Users/christian/opt/payara41/glassfish/lib/templates/logging.properties
#!## LogManagerService.postConstruct : dest=/Users/christian/opt/payara41/glassfish/domains/payaradomain/config/logging.properties
Info: Running Payara Version: Payara Server 4.1.1.164 #badassfish (build 28)
Info: Server log file is using Formatter class: com.sun.enterprise.server.logging.ODLLogFormatter
Info: Registered org.glassfish.ha.store.adapter.cache.ShoalBackingStoreProxy for persistence-type = replicated in BackingStoreFactoryRegistry
Info: Authorization Service has successfully initialized.
Info: Realm [admin-realm] of classtype [com.sun.enterprise.security.auth.realm.file.FileRealm] successfully created.
Info: Realm [file] of classtype [com.sun.enterprise.security.auth.realm.file.FileRealm] successfully created.
Info: Realm [certificate] of classtype [com.sun.enterprise.security.auth.realm.certificate.CertificateRealm] successfully created.
Info: Registered fish.payara.ha.hazelcast.store.HazelcastBackingStoreFactoryProxy for persistence-type = hazelcast in BackingStoreFactoryRegistry
Info: Registered Hazelcast BackingStoreFactory with persistence-type = hazelcast
Info: Grizzly Framework 2.3.28 started in: 47ms - bound to [/0.0.0.0:8080]
Info: Grizzly Framework 2.3.28 started in: 1ms - bound to [/0.0.0.0:8181]
Info: Grizzly Framework 2.3.28 started in: 2ms - bound to [/0.0.0.0:4848]
Info: Grizzly Framework 2.3.28 started in: 1ms - bound to [/0.0.0.0:3700]
Info: Payara Server 4.1.1.164 #badassfish (28) startup time : Felix (33 542ms), startup services(5 715ms), total(39 257ms)
Info: Payara Notification Service Started with configuration: NotificationExecutionOptions{enabled=true, notifierConfigurationExecutionOptionsList={LOG=NotifierConfigurationExecutionOptions{notifierType=LOG, enabled=true}}}
Info: Cleaning JarFileFactory Cache to prevent jar FD leaks
Info: HV000001: Hibernate Validator 5.1.2.Final
Info: Grizzly Framework 2.3.28 started in: 1ms - bound to [/0.0.0.0:7676]
Info: Registered com.sun.enterprise.glassfish.bootstrap.osgi.EmbeddedOSGiGlassFishImpl#7bca6fac as OSGi service registration: org.apache.felix.framework.ServiceRegistrationImpl#129fed45.
Info: /Users/christian/opt/payara41/glassfish/domains/payaradomain/autodeploy/bundles does not exist, please create it.
Info: JMXStartupService has started JMXConnector on JMXService URL service:jmx:rmi://192.168.0.183:8686/jndi/rmi://192.168.0.183:8686/jmxrmi
Is there any security mechanism that prevents this on Mac OS?
It seems that Netbeans cannot connect to the started Payara Server. Maybe your issue is similar to this one with Netbeans and Tomcat on a Mac after some system update: https://discussions.apple.com/thread/7680039?start=0&tstart=0
Here is a quote from that page:
Step 1: Go to system preference >Network>Select your wifi
connection>Advanced>select proxies tab.
There check 3 options 1) Auto proxy Discovery 2)Automatic Proxy
configuration 3) web proxy(http)
Step 2: Go to Netbeans>preferences>General> select use system proxy>
reload> test connection
I found an alternative solution for me:
Go to Netbeans-> Preference-> chose No Proxy.
Test the connection. should success, Press Ok. Then clean and run the application.
No need to change any network configuration on mac.
Setup a new angular project under linux. Committed it to git and cloned it to windows. Using bower and npm, I managed to get everything loaded, except, I have this one error (only on windows)
A recursive grep for ../time/convert in the project shows me:
./node_modules/grunt-contrib-imagemin/node_modules/gifsicle/node_modules/bin-wrapper/node_modules/mout/date/diff.js:var convert = require('../time/convert');
./node_modules/grunt-contrib-imagemin/node_modules/gifsicle/node_modules/bin-wrapper/node_modules/mout/src/date/diff.js:define(['./totalDaysInMonth', './totalDaysInYear', '../time/convert'], function(totalDaysInMonth, totalDaysInYear, convert){
./node_modules/grunt-contrib-imagemin/node_modules/optipng-bin/node_modules/bin-wrapper/node_modules/mout/date/diff.js:var convert = require('../time/convert');
./node_modules/grunt-contrib-imagemin/node_modules/pngquant-bin/node_modules/bin-wrapper/node_modules/mout/date/diff.js:var convert = require('../time/convert');
./node_modules/grunt-contrib-imagemin/node_modules/pngquant-bin/node_modules/bin-wrapper/node_modules/mout/src/date/diff.js:define(['./totalDaysInMonth', './totalDaysInYear', '../time/conve
but ls -l shows:
$ ls ./node_modules/grunt-contrib-imagemin/node_modules/gifsicle/node_modules/bin-wrapper/node_modules/mout/time
convert.js now.js parseMs.js toTimeString.js
Which says that convert.js is actually there. Being new to grunt and angular, I'm puzzled where this could be coming from and how to troubleshoot it.
After this I end up getting stuck here:
Running "karma:unit" (karma) task
INFO [karma]: Karma v0.10.4 server started at http://localhost:8080/
INFO [launcher]: Starting browser Chrome
WARN [watcher]: Pattern ".../test/mock/**/*.js" does not match any file
WARN [launcher]: Chrome have not captured in 60000 ms, killing.
INFO [launcher]: Trying to start Chrome again.
WARN [launcher]: Chrome have not captured in 60000 ms, killing.
INFO [launcher]: Trying to start Chrome again.
Wondering if angular work using grunt is just not possible on Windows....
My solution was to quit using windows. Moved dev work to linux, and no more crazy problems like this. Oh, and my machine now seems a good deal faster too.
I'm having a setup where I run JBehave tests during a Maven build.
Test steps include sending requests to a web service with the SoapUI Java classes.
Everything is working fine, testwise. My problem is that the SoapUI part of the progress seems to overwrite the log4j settings so that subsequent log calls doesn't get printed to console (nor files).
I've tried the workaround where I call
ClassLoader loader = this.getClass().getClassLoader();
URL resource = loader.getResource("log4j.xml");
PropertyConfigurator.configure(resource);
to try to reset the configuration to my original one, but no success so far.
Log4j (1.2) and SoapUI (4.5.1) uses plain settings in pom. The logger is created as
protected final Log log = LogFactory.getLog(getClass());
The console output I get follows:
pool-1-thread-1 16:36:08,212 DEBUG ästeps.LoginSteps:25 - logging in user: testfir
pool-1-thread-1 16:36:08,213 DEBUG äpages.LoginPage:26 - Create LoginPage
pool-1-thread-1 16:36:08,985 DEBUG äpages.LoginPage:38 - login user: testfir
pool-1-thread-1 16:36:10,343 DEBUG äpages.WorkspacePage:36 - creating WorkspacePage
Givet user testfir has logged in
16:36:11,634 WARN [SoapUI] Missing folder [D:\proj\src\test\functional-tests\.\ext] for external libraries
16:36:11,809 INFO [DefaultSoapUICore] initialized soapui-settings from [C:\Users\xxx\soapui-settings.xml]
16:36:12,176 INFO [WsdlProject] Loaded project from [file:/D:/proj/src/test/functional-tests/src/test/resources/ReceiveCase-soapui.xml]
16:36:12,640 DEBUG [HttpClientSupport$SoapUIHttpClient] Attempt 1 to execute request
16:36:12,640 DEBUG [SoapUIMultiThreadedHttpConnectionManager$SoapUIDefaultClientConnection] Sending request: POST /soa-infra/services/default/ReceiveCases/ReceiveCase_v1_0_ep HTTP/1.1
16:36:13,841 DEBUG [SoapUIMultiThreadedHttpConnectionManager$SoapUIDefaultClientConnection] Receiving response: HTTP/1.1 200 OK
16:36:13,842 DEBUG [HttpClientSupport$SoapUIHttpClient] Connection can be kept alive indefinitely
And a case exists
When case is choosen
16:36:46,832 DEBUG [SoapUIMultiThreadedHttpConnectionManager$SoapUIDefaultClientConnection] Connection closed
Then the details are displyed
And I'm expecting a log output with
Setting case Id to: 123456
in the same manner as "Create login page".
Can't understand why this is and what to do to get my log entries to show up. Any ideas out there?
Best regards, Christian
Managed to find the root of the problem.
It was Maven that distorted the file encoding. Adding
<configuration>
<encoding>UTF-8</encoding>
<inputEncoding>UTF-8</inputEncoding>
<outputEncoding>UTF-8</outputEncoding>
<argLine>-Dfile.encoding=UTF-8</argLine>
</configuration>
to the maven-surefire-plugin part in pom file solved my issue.
/Cheers