Menu
▾
▴
#317 Crash of wrapper-windows-x86-32.exe on Windows 2012R2
Hi,
On one site, during deployment, the wrapper crash two times with not identified context and without any logging data or dump file.
It was running on console mode.
I have restarted it with debug level logging as a service.
The only information I have are from windows application events :
Nom de l’application défaillante wrapper-windows-x86-32.exe, version : 3.5.46.0, horodatage : 0x6130f38e
Nom du module défaillant : wrapper-windows-x86-32.exe, version : 3.5.46.0, horodatage : 0x6130f38e
Code d’exception : 0xc0000409
Décalage d’erreur : 0x0003a8d9
ID du processus défaillant : 0xf0c
Heure de début de l’application défaillante : 0x01d7e1f94fd729b3
Chemin d’accès de l’application défaillante : C:\srv\lib\wrapper-windows-x86-32.exe
Chemin d’accès du module défaillant: C:\srv\lib\wrapper-windows-x86-32.exe
Any advice on what to do ?
Thanks
Hello
Thank you for reporting this issue.
Do you have some log in the wrapper.log file ? If possible can you send them to support@tanukisoftware.com?
A possible cause is that the Wrapper is being killed by an external process. To trace which process initiated the kill, you may set the wrapper.monitor_exit and wrapper.java.monitor_exit properties as explained on this page: https://wrapper.tanukisoftware.com/doc/english/props-monitor-exit.html (please follow the steps to first register the Wrapper with the --setup command)
This should show the reason as a message in the Event Viewer.
You already have a record in the event viewer, but does it also show a message describing the error? (in the General or Details tabs).
If this still doesn't help, can you try executing an older version of the Wrapper in the same context to see if the problem is the same?
Best Regards,
Maxime
Hello again
Sorry I just noticed the wrapper.monitor_exit and wrapper.java.monitor_exit properties are not available in the Community Edition. They are part of the Standard Edition.
However, if you are able to reproduce the crash quite quickly after starting the Wrapper, you may use the Standard binaries for testing with a 15-min timed license. The 15-min trial license is included in all packages, applies by default, and allows you to run the Wrapper for up to 15min. This should hopefully be enough to help you debug the issue.
If you need more time to reproduce the issue, you can also request for a 1 month trial license.
Best Regards,
Maxime