|Anonymous | Login | Signup for a new account||10-02-2023 18:29 PDT|
|Main | My View | View Issues | Change Log | Docs|
|Viewing Issue Advanced Details [ Jump to Notes ]||[ View Simple ] [ Issue History ] [ Print ]|
|ID||Category||Severity||Reproducibility||Date Submitted||Last Update|
|0000878||[Resin]||minor||always||01-19-06 09:17||01-20-06 15:07|
|ETA||none||Fixed in Version||3.0.18||Product Version||3.0.17|
|Summary||0000878: abrupt shutdown on windows|
(rep by Mark Lai)
2. Stopping Resin does not go through the WebApps stop lifecycle. The server just shuts down abruptly. So the webapps are not stopped and the servlets not destroyed. WinXP Pro task manager shows java process ended. The server is controlled using httpd.exe.
I also tried 3.0.14, which does not have this problem.
|Steps To Reproduce|
I did some digging on the abrupt server shutdown. The problem appears to be a shared data read on ResinServer's lifecycle, between the main thread and the resin-destroy thread. As soon as the resin-destory thread sets the lifecycle state to IS_DESTROYING, the main thread picks up the new state and determines that the server has been "closed". Then it exits the JVM.
By suspending the main thread during debugging, I was able to get the proper stop/destroy behavior from the resin-destroy thread.
|Lifecycle and ResinServer needed updating to distinguish between the destroying state and the destroyed state.|
|01-19-06 09:17||ferg||New Issue|
|01-20-06 08:54||ferg||Note Added: 0000750|
|01-20-06 15:07||ferg||Note Added: 0000752|
|01-20-06 15:07||ferg||Assigned To||=> ferg|
|01-20-06 15:07||ferg||Status||new => closed|
|01-20-06 15:07||ferg||Resolution||open => fixed|
|01-20-06 15:07||ferg||Fixed in Version||=> 3.0.18|
| Mantis 1.0.0rc3[^]
Copyright © 2000 - 2005 Mantis Group
30 total queries executed.|
26 unique queries executed.