Activity for Yet Another Java Service Wrapper
-
Rich DiCroce posted a comment on discussion Open Discussion
@rzorzorzo Is there any progress towards getting Groovy to work on Java 25? I have some applications I'd like to upgrade, but they need the Groovy scripting to work.
-
Juan Marques posted a comment on discussion Open Discussion
I will keep you posted , I will be testing early next week , but honestly not expecting issues.
-
rzo posted a comment on discussion Open Discussion
not yet. but i think it should work if you rename the path to groovy in the classpath. if you are having issues, pls let me know. -- Ron
-
Hello @rzorzorzo , Have you tried running with java 25 already?
-
tyoma53 posted a comment on discussion Open Discussion
hello, i can confirm that yajsw 13.18 works fine with OpenJDK 21 from Eclipse on CentOS 9. we're using it with ActiveMQ, and have no problems with it. only issues i see in log messages are below: Unable to classify GarbageCollectorMXBean [ZGC Minor Cycles] Unable to classify GarbageCollectorMXBean [ZGC Minor Pauses] Unable to classify GarbageCollectorMXBean [ZGC Major Cycles] Unable to classify GarbageCollectorMXBean [ZGC Major Pauses] GC configuration is -XX:+UseZGC -XX:+ZGenerational thank you...
-
thanks.
-
yajsw-stable-13.18 released
-
Lutz Bergmann posted a comment on discussion Open Discussion
On the news page https://sourceforge.net/p/yajsw/news/ the Entry for version 13.18 is mislabeled as version 17.17 (I assume). Could you please fix that?
-
xiyz created ticket #63
Unable to classify GarbageCollectorMXBean [G1 Concurrent GC]
-
Rares posted a comment on ticket #34
Thanks to your indication to use runConsole.bat, I was able to get to the root of it: an removed java command line option (-Xnoagent) was crashing the jvm startup. However, this unrooted a bug: the Java startup error was displayed and written to service.log with runConsole.bat, but it is not displayed or written to service.log using service mode. service mode: WARNING|wrapper|Service Test Project|25-10-17 18:23:44|YAJSW: yajsw-stable-13.18 WARNING|wrapper|Service Test Project|25-10-17 18:23:44|OS...
-
Q: 1. are you sure your app can run with the OS and JDK 25 without the wrapper ? 2. before running as service, did you try runConsole.bat ? pls run using runConsole and with pipestreams and wrapper.debug and post the output of the windows console.
-
Hello, I appreciate your answer. 1. The solution described in https://sourceforge.net/p/yajsw/discussion/810310/thread/d90b30628c/#919a is not sufficient. I got past the groovy problem by renaming the groovy folders and disabled the script, but the wrapped process stopped as soon as it started: WARNING|wrapper|Service Test Project|25-10-16 10:54:37|YAJSW: yajsw-stable-13.18 WARNING|wrapper|Service Test Project|25-10-16 10:54:37|OS : Windows Server 2022/10.0/amd64 WARNING|wrapper|Service Test Project|25-10-16...
-
pls check this out: https://sourceforge.net/p/yajsw/discussion/810310/thread/d90b30628c/#919a for the roadmap pls check the readme.txt.
-
yes, jdk 21 is supported. if you have issues and need help pls provide more details: OS, jdk, conf file, log output.
-
Eason Li posted a comment on discussion Open Discussion
Does the latest version 13.18 support the Java 21? I try it, maybe it not works...
-
Crashes on JDK 25
-
Thank you. My app started normally, and the issue was fixed in release 13.18
-
Could not start the app when upgrading from 13.15 to 13.17
-
release 13.18
-
yajsw-stable-13.17 released
-
Yet Another Java Service Wrapper released /yajsw/yajsw-stable-13.18/yajsw-stable-13.18.zip
-
-
release 13.18
-
Hi, I can reproduce it. These logs are closer to the complete logs and my config my config: # WARNING - Do not modify any of the properties when an application # using this configuration file has been installed as a service or daemon. # Please uninstall the service before modifying this file. The # service must then be reinstalled. #******************************************************************** # Java Executable Properties #********************************************************************...
-
These logs are closer to the complete logs and my config my config: # WARNING - Do not modify any of the properties when an application # using this configuration file has been installed as a service or daemon. # Please uninstall the service before modifying this file. The # service must then be reinstalled. #******************************************************************** # Java Executable Properties #******************************************************************** # Java Application wrapper.java.command=java...
-
These logs are closer to the complete logs and my config my config: WARNING - Do not modify any of the properties when an application using this configuration file has been installed as a service or daemon. Please uninstall the service before modifying this file. The service must then be reinstalled. ********** Java Executable Properties ********** Java Application wrapper.java.command=java ********** @home@ ********** wrapper.working.dir=${myapp_home} Java Main class. YAJSW: default is "org.rzo.yajsw.app.WrapperJVMMain"...
-
Overall, after upgrading to 13.17, the application fails to start.
-
Yes, I saw it too
-
yes
-
OS: ubuntu 20.04 sorry I can't reproduce it no longer
-
ps: however, while testing, i see there is an issue on posix systems: java.lang.NoClassDefFoundError: io/netty/util/internal/logging/InternalLoggerFactory this requires a new release.
-
ps: the exception is only logged in case wrapper.debug is set to true
-
hello, works for me. i am not getting this error. OS ? checking the code: this is just a warning. your application should be starting just fine. if this is not the case: pls provide the full log. and config. remember to remove private data such as passwords from these files before posting. -- Ron
-
Could not start the app when upgrading from 13.15 to 13.17
-
thanks for pointing this out. something went wrong during the packing of the zip file. release 13.17
-
Netty* v4.1.118 vulnerability
-
release 13.17
-
yajsw-stable-13.17 released
-
-
-
13.17 regression test
-
release 13.17
-
release 13.17
-
A Yarborough posted a comment on ticket #38
Hi rzo - Thank you for patching for v13.x. I unzipped release v13.16 but these two libs are not patched still: inflating: yajsw-stable-13.16/lib/core/commons/commons-lang-2.6.jar inflating: yajsw-stable-13.16/lib/core/commons/commons-lang3-3.12.0.jar Thank you agian.
-
REVATHI V posted a comment on ticket #39
https://nvd.nist.gov/vuln/detail/CVE-2025-55163 https://nvd.nist.gov/vuln/detail/CVE-2025-58056 https://nvd.nist.gov/vuln/detail/CVE-2025-58057
-
Netty* v4.1.118 vulnerability
-
netty-common-4.1.114.Final vulnerability
-
commons-vfs2-2.9.0.jar Vulnerabilities
-
YAJSW v13.x: commons-lang3 & commons-lang vulnerability
-
release 13.16
-
yajsw-stable-13.16 released
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
release 13.16
-
YAJSW v13.x: commons-lang3 & commons-lang vulnerability
-
netty* v4.1.118 is included with yajsw v13.15. Thank you, rzo!
-
The fix v2.10.0 is included in yajsw v13.15. Thank you, rzo.
-
Hi: When starting and stopping, the following log messages appear, They are a bit verbose — how can I control or hide them? My current wrapper.console.format=M I also tried: wrapper.console.format= But it didn’t work. example log message YAJSW: yajsw-stable-13.15 OS : Linux/6.14.10-orbstack-00291-g1b252bd3edea/aarch64 JVM : Ubuntu/11.0.27//usr/lib/jvm/java-11-openjdk-arm64/64 Looking in classpath from org.rzo.yajsw.boot.WrapperClassLoader@725bef66 for /com/sun/jna/linux-aarch64/libjnidispatch.so...
-
Thank you , remote debug working now
-
this is described in the documentation. set it to the port which you intend to attach to with the debugger. -- Ron
-
I understand that setting wrapper.java.debug.port will adjust the timeouts automatically during debugging. What value should I assign to wrapper.java.debug.port to make remote debugging work properly?
-
hello, the problem is, that in default mode yajsw is checking some timing conditions. during debugging these cannot be met and yajsw will restart the process. by setting the property wrapper.java.debug.port the timeouts are overwritten, so that the application process can be interrupted for debugging. -- Ron
-
UPDATE: Remote debugging is now connected, and the configuration is wrapper.java.additional.15=-agentlib:jdwp=transport=dt_socket\,server=y\,suspend=n\,address=*:8000 But the debugger always disconnects automatically ， how to fix it？ ORIGIN: I'm preparing for remote debugging. I tried adding the following configuration to wrapper.conf: wrapper.java.additional.15=-agentlib:jdwp=transport=dt_socket\,server=y\,suspend=n\,address=*:5005 but found that the application failed to start. After removing the...
-
UPDATE: Remote debugging is now connected, and the configuration is wrapper.java.additional.15=-agentlib:jdwp=transport=dt_socket\,server=y\,suspend=n\,address=*:8000 But the debugger always disconnects automatically ， how to fix it？ ORIGIN: I'm preparing for remote debugging. I tried adding the following configuration to wrapper.conf: wrapper.java.additional.15=-agentlib:jdwp=transport=dt_socket\,server=y\,suspend=n\,address=*:5005 but found that the application failed to start. After removing the...
-
ORIGIN: I'm preparing for remote debugging. I tried adding the following configuration to wrapper.conf: wrapper.java.additional.15=-agentlib:jdwp=transport=dt_socket\,server=y\,suspend=n\,address=*:5005 but found that the application failed to start. After removing the above configuration, it started normally. Then I tried adding: wrapper.java.additional.15=-agentlib:jdwp=transport=dt_socket\,server=y\,suspend=n\,address=*:5005 wrapper.java.debug.port=5005 It still failed to start, but after removing...
-
I'm preparing for remote debugging. I tried adding the following configuration to wrapper.conf: wrapper.java.additional.15=-agentlib:jdwp=transport=dt_socket\,server=y\,suspend=n\,address=*:5005 but found that the application failed to start. After removing the above configuration, it started normally. Then I tried adding: wrapper.java.additional.15=-agentlib:jdwp=transport=dt_socket\,server=y\,suspend=n\,address=*:5005 wrapper.java.debug.port=5005 It still failed to start, but after removing the...
-
I'm preparing for remote debugging. I tried adding the following configuration to wrapper.conf: wrapper.java.additional.15=-agentlib:jdwp=transport=dt_socket\,server=y\,suspend=n\,address=*:5005 but found that the application failed to start. After removing the above configuration, it started normally. Then I tried adding: wrapper.java.additional.15=-agentlib:jdwp=transport=dt_socket\,server=y\,suspend=n\,address=*:5005 wrapper.java.debug.port=5005 It still failed to start, but after removing the...
-
Thank you for the suggestion — I found the issue. It wasn't a JNA version conflict; it was a mistake I made when setting the classpath.
-
just tested it on win 11 and it works for me. note that there should be no conflict between the jna version provided by yajsw and yours, as both run in different processes/class-loaders. here an extract from my wrapper.conf: wrapper.java.command = C:\\java\\jdk11.0.18_10\\bin\\java wrapper.java.classpath.1 = lib/*.jar contents of lib folder: jna-5.9.0.jar jna-platform-5.9.0.jar oshi-core-5.8.2.jar OshiYajswTest-0.0.1-SNAPSHOT.jar slf4j-api-1.7.32.jar here output in the log file: WARNING|wrapper|test.SystemInfoExample|25-06-26...
-
just tested it on win 11 and it works for me. note that there should be no conflict between the jna version provided by yajsw and yours, as both run in different processes/class-loaders. here an extract from my wrapper.conf: wrapper.java.command = C:\\java\\jdk11.0.18_10\\bin\\java wrapper.java.classpath.1 = lib/*.jar contents of lib folder: jna-5.9.0.jar jna-platform-5.9.0.jar oshi-core-5.8.2.jar OshiYajswTest-0.0.1-SNAPSHOT.jar slf4j-api-1.7.32.jar here output in the log file: WARNING|wrapper|test.SystemInfoExample|25-06-26...
-
add some jna log to start logger.info("JNA version: {}", com.sun.jna.Native.VERSION); logger.info("JNA Platform: {}", Platform.getOSType()); output: JNA version: 5.9.0 JNA Platform: 1
-
Yajsw log message: Looking in classpath from org.rzo.yajsw.boot.WrapperClassLoader@c39f790 for /com/sun/jna/win32-x86-64/jnidispatch.dll Found library resource at jar:file:/E:/tmp/devgrip-11.9.10/boot/./lib/core/jna/jna-5.12.1.jar!/com/sun/jna/win32-x86-64/jnidispatch.dll
