rzo

Now i found out that when i set wrapper.console.pipestreams = false then i can start / stop the app pipestreams is only intended for testing and should not be used in production. however the app should run as service and console with or without it. if it does not run as a service with pipestreams set, then this may indicate that there is an issue with user rights. Only one Exception Message in then wrapper.log occurs. Have you an idea why? this may be the same issue as above. the wrapped app is opening...

Now i found out that when i set wrapper.console.pipestreams = false then i can start / stop the app pipestreams is only intended for testing and should not be used in production. however the app should run as service and console with or without it. if it does not run as a service with pipestreams set, then this may indicate that there is an issue with user rights. Only one Exception Message in then wrapper.log occurs. Have you an idea why? this may be the same issue as above. the wrapped app is opening...

Now i found out that when i set wrapper.console.pipestreams = false then i can start / stop the app pipestreams is only intended for testing and should not be used in production. however the app should run as service and console with or without it. if it does not run as a service with pipestreams set, then this may indicate that there is an issue with user rights. Only one Exception Message in then wrapper.log occurs. Have you an idea why? this may be the same issue as above. the wrapped app is opening...

the netty vulnerabilities concern the http implementation, the jar of which is not included with yajsw. so this is not critical. an update will follow in the next release. updating netty, or groovy is not that simple, as some classes are shadowed in yajsw: https://sourceforge.net/p/yajsw/yajsw/ci/master/tree/src/yajsw/src/main/java/io/netty/ when updating jars one has to update the manifest file: https://sourceforge.net/p/yajsw/yajsw/ci/master/tree/build/MANIFEST.MF -- Ron

thanks for the feedback. there seems to be an issue with groovy 4 and java 22. weird, i thought i tested the latest version with java 22. in your case: according to your config you do not need groovy. simple interpolation is sufficient. so as a workaround go to lib/extended and just rename the folder groovy to for example groovyx. this will result in an error that groovy is missing, but the application should run as expected. let me know if this helps. -- Ron

hello, pls upload your configuration and the resulting log file. remember to remove passwords or other private data from the files before uploading. -- Ron

hello, pls check if your app is java 21 compatible by running it with java 21 without the wrapper. before running as service try running it as console, by calling bat/runConsole.bat the logging suggests that there is an issue launching the java sub process. to see some more logging as to why your app does not launch pls set in the conf file the following: wrapper.console.pipestreams = true then run as console and check the console output. -- Ron

jackson-core-2.11.3 - vulnerability