Activity for teapot418
-
teapot418 posted a comment on ticket #201
yes, Issue is solved, thank you.
-
hello, I have tried this in new release 13.11, but nothing changed, problem still continues Regards Monika
-
wrapper.on_exit SHUTDOWN doesn't work
-
Thank you for fixing WIFEXITED/WIFSIGNALED in release 13.05 Regards Monika
-
Hello, thank you for fixing the issue with logging I mentioned. However, functions WIFEXITED and WIFSIGNALED in release 13.04 are identical, I'm afraid this will not work correctly. definitions in waitstatus.h are like this #define __WIFEXITED(status) (__WTERMSIG(status) == 0) #define __WIFSIGNALED(status) (((signed char) (((status) & 0x7f) + 1) >> 1) > 0) I think this is the correct way to define them. Regards Monika
-
Hello, thank you for response, In the end, the action that was done in my reported case was restart. I looked into wrapper source code, I think I found the code, that leads to the mentioned sequence of lines in the log file (WrappedJavaProcess.java, killedRestartHandler) if ((allowRestart() && exitCodeRestart() && !exitCodeShutdown() && !exitCodeStop()) || (allowRestart() && exitSignalRestart() && !exitSignalShutdown() && !exitSignalStop())) { restartInternal("controller killed restart handler");...
-
Hello, I would like to ask, how to read this log information, what is the real cause of wrapper restart? exit code rule? signal code rule? What happens if a rule for the exit code and signal code contradict each other? 22-05-06 04:41:55|exit code posix process: 15 application(status/signal): 0/15 22-05-06 04:41:55|restart process due to default exit code rule 22-05-06 04:41:55|shutdown wrapper due to exit code rule 22-05-06 04:41:55|restart process due to default signal code rule 22-05-06 04:41:55|restart...
1