Hi folks,
What's the roadmap to support JDK25?
1. Core YAJSW fails without any log messages, the child process just exits.
2. Groovy scripts fail with the message "Unsupported class file format 69".
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 10:54:37|JVM : Azul Systems, Inc./25/C:\Program Files (x86)\Test\System\Java/64
INFO|wrapper|Service Test Project|25-10-16 10:54:37|start delay: 0
INFO|wrapper|Service Test Project|25-10-16 10:54:38|started process with pid 6372
INFO|wrapper|Service Test Project|25-10-16 10:54:38|restart internal RUNNING controller killed restart handler
INFO|wrapper|Service Test Project|25-10-16 10:54:38|stopping process with pid/timeout 6372 45000
INFO|wrapper|Service Test Project|25-10-16 10:54:38|process exit code: 1
This is with wrapper.console.pipestreams = true
Please let me know if you need other logs.
By roadmap I mean the scheduled Expected Time of Arrival for version 14.0
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
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 : Windows Server 2022/10.0/amd64
WARNING|wrapper|Service Test Project|25-10-17 18:23:44|JVM : Azul Systems, Inc./25/C:\Program Files (x86)\Test\System\Java/64
INFO|wrapper|Service Test Project|25-10-17 18:23:44|start delay: 0
INFO|wrapper|Service Test Project|25-10-17 18:23:44|started process with pid 7600
INFO|wrapper|Service Test Project|25-10-17 18:23:44|restart internal RUNNING controller killed restart handler
INFO|wrapper|Service Test Project|25-10-17 18:23:44|stopping process with pid/timeout 7600 45000
INFO|wrapper|Service Test Project|25-10-17 18:23:45|process exit code: 1
console mode:
WARNING|wrapper|Test Project|25-10-17 18:28:30|YAJSW: yajsw-stable-13.18
WARNING|wrapper|Test Project|25-10-17 18:28:30|OS : Windows Server 2022/10.0/amd64
WARNING|wrapper|Test Project|25-10-17 18:28:30|JVM : Azul Systems, Inc./25/c:\Program Files (x86)\Test\System\Java/64
INFO|wrapper|Test Project|25-10-17 18:28:30|started process with pid 1448 INFO|1448/0|Test Project|25-10-17 18:28:30|Unrecognized option: -Xnoagent
INFO|1448/0|Test Project|25-10-17 18:28:30|Error: Could not create the Java Virtual Machine.
INFO|1448/0|Test Project|25-10-17 18:28:30|Error: A fatal exception has occurred. Program will exit.
*INFO|wrapper|Test Project|25-10-17 18:28:30|restart internal RUNNING controller killed restart handler
INFO|wrapper|Test Project|25-10-17 18:28:30|stopping process with pid/timeout 1448 45000
INFO|wrapper|Test Project|25-10-17 18:28:31|process exit code: 1
messages only present in console mode, could use a stdout redirect:
WARNING: A terminally deprecated method in sun.misc.Unsafe has been called
WARNING: sun.misc.Unsafe::objectFieldOffset has been called by com.nqzero.permit.Permit (file:/C:/ProgramData/Test/a6215ffe/Yajsw/./lib/core/permit/permit-reflect-0.4.jar)
WARNING: Please consider reporting this to the maintainers of class com.nqzero.permit.Permit
WARNING: sun.misc.Unsafe::objectFieldOffset will be removed in a future release
YAJSW: yajsw-stable-13.18
OS : Windows Server 2022/10.0/amd64
JVM : Azul Systems, Inc./25/c:\Program Files (x86)\Test\System\Java/64
WARNING: A restricted method in java.lang.System has been called
WARNING: java.lang.System::load has been called by com.sun.jna.Native in an unnamed module (file:/C:/ProgramData/Test/a6215ffe/Yajsw/wrapper.jar)
WARNING: Use --enable-native-access=ALL-UNNAMED to avoid a warning for callers in this module
WARNING: Restricted methods will be blocked in a future release unless native access is enabled
wrapper.logfile.umask -1
initOutputFiles: -1
open umask -1
Thanks for all your help!
P.S. Any release date for v14?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
pls check this out:
https://sourceforge.net/p/yajsw/discussion/810310/thread/d90b30628c/#919a
for the roadmap pls check the readme.txt.
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 10:54:37|JVM : Azul Systems, Inc./25/C:\Program Files (x86)\Test\System\Java/64
INFO|wrapper|Service Test Project|25-10-16 10:54:37|start delay: 0
INFO|wrapper|Service Test Project|25-10-16 10:54:38|started process with pid 6372
INFO|wrapper|Service Test Project|25-10-16 10:54:38|restart internal RUNNING controller killed restart handler
INFO|wrapper|Service Test Project|25-10-16 10:54:38|stopping process with pid/timeout 6372 45000
INFO|wrapper|Service Test Project|25-10-16 10:54:38|process exit code: 1
This is with wrapper.console.pipestreams = true
Please let me know if you need other logs.
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.
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 : Windows Server 2022/10.0/amd64
WARNING|wrapper|Service Test Project|25-10-17 18:23:44|JVM : Azul Systems, Inc./25/C:\Program Files (x86)\Test\System\Java/64
INFO|wrapper|Service Test Project|25-10-17 18:23:44|start delay: 0
INFO|wrapper|Service Test Project|25-10-17 18:23:44|started process with pid 7600
INFO|wrapper|Service Test Project|25-10-17 18:23:44|restart internal RUNNING controller killed restart handler
INFO|wrapper|Service Test Project|25-10-17 18:23:44|stopping process with pid/timeout 7600 45000
INFO|wrapper|Service Test Project|25-10-17 18:23:45|process exit code: 1
console mode:
WARNING|wrapper|Test Project|25-10-17 18:28:30|YAJSW: yajsw-stable-13.18
WARNING|wrapper|Test Project|25-10-17 18:28:30|OS : Windows Server 2022/10.0/amd64
WARNING|wrapper|Test Project|25-10-17 18:28:30|JVM : Azul Systems, Inc./25/c:\Program Files (x86)\Test\System\Java/64
INFO|wrapper|Test Project|25-10-17 18:28:30|started process with pid 1448
INFO|1448/0|Test Project|25-10-17 18:28:30|Unrecognized option: -Xnoagent
INFO|1448/0|Test Project|25-10-17 18:28:30|Error: Could not create the Java Virtual Machine.
INFO|1448/0|Test Project|25-10-17 18:28:30|Error: A fatal exception has occurred. Program will exit.
*INFO|wrapper|Test Project|25-10-17 18:28:30|restart internal RUNNING controller killed restart handler
INFO|wrapper|Test Project|25-10-17 18:28:30|stopping process with pid/timeout 1448 45000
INFO|wrapper|Test Project|25-10-17 18:28:31|process exit code: 1
messages only present in console mode, could use a stdout redirect:
WARNING: A terminally deprecated method in sun.misc.Unsafe has been called
WARNING: sun.misc.Unsafe::objectFieldOffset has been called by com.nqzero.permit.Permit (file:/C:/ProgramData/Test/a6215ffe/Yajsw/./lib/core/permit/permit-reflect-0.4.jar)
WARNING: Please consider reporting this to the maintainers of class com.nqzero.permit.Permit
WARNING: sun.misc.Unsafe::objectFieldOffset will be removed in a future release
YAJSW: yajsw-stable-13.18
OS : Windows Server 2022/10.0/amd64
JVM : Azul Systems, Inc./25/c:\Program Files (x86)\Test\System\Java/64
WARNING: A restricted method in java.lang.System has been called
WARNING: java.lang.System::load has been called by com.sun.jna.Native in an unnamed module (file:/C:/ProgramData/Test/a6215ffe/Yajsw/wrapper.jar)
WARNING: Use --enable-native-access=ALL-UNNAMED to avoid a warning for callers in this module
WARNING: Restricted methods will be blocked in a future release unless native access is enabled
wrapper.logfile.umask -1
initOutputFiles: -1
open umask -1
Thanks for all your help!
P.S. Any release date for v14?