Am 27.04.2006 19:05 Uhr schrieb "Chuck Hill" unter <[EMAIL PROTECTED]>:
> > On Apr 27, 2006, at 12:37 AM, Wolfram Stebel wrote: > >> Hi List, >> >> i have a WOApp running in 7 instances. Each night i scheduled one >> of them to >> restart at 3AM. >> When i come to the server in the morning, one instance (the >> scheduled one) >> shows "refuse new session=ON" but there is no new log for the instance >> showing up after restart. >> So i suspect that the restart failes, only the refuse is set and >> nothing >> more. >> > I think you are probably mis-interpreting what is happening. The > application will not restart until all of the sessions have > terminated (unless you have configured it to restart when there are > some number of remaining sessions). What are you describing is what > happens when sessions get hung / deadlocked. Sessions in this state > are never checked back in and so never terminate. As the sessions > don't terminate, neither does the app. It just sits there in > shutdown mode waiting for the sessions to terminate and they never > will. So the problem is not that your app is not restarting, but > that it is not actually stopping! > > I would suggest getting a thread dump from the application when it > is in this state, that should diagnose the problem. In your code, > the first thing to ensure is that the constructor, awake, sleep, and > terminate methods of session can't throw an exception ever. > > Chuck Thanks Chuck and Jerry, as you wrote (but how could you know? :-) ), there have been a lot open sessions in each of the instances. There has been another "infect" in my application, it always returned to the previous page on a browser refresh... The Barbarian solution: I simply restarted the server and everything seems to be fine again, also the refresh problem. But... You can't do this too often on a production server :-) Is there a simple way to monitor the sessions without coding tons of lines? Is there a default set of information one should log in it's application, in addition to the logs of the application logic? As WO development is fairly documented (with Practical WebObjects :-) ), deployment and maintenance of WO applications is not. Shure, most of us are developers... :-) but shouldn't the applications run somewhere for profit too? Is it worth another book from Chuck and Sacha? Regards and Thanks Wolfram _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to archive@mail-archive.com
