help decipher log entry
Hi, I have a tomcat server running a lone java application on vms. The problem is that it shuts down occasionally for seemingly no reason. Could somebody help shed some light on the following log snippet - it's the entry right before the shutdown happens. I'm really a novice when it comes to java web programming and I'm trying to wrap my head around all this. Thanks for any help, Paul snip StandardServer.await: accept: java.io.InterruptedIOException: Accept timed out java.io.InterruptedIOException: Accept timed out at java.net.PlainSocketImpl.socketAccept(Native Method) at java.net.PlainSocketImpl.accept(PlainSocketImpl.java, Compiled Code) at java.net.ServerSocket.implAccept(ServerSocket.java, Compiled Code) at java.net.ServerSocket.accept(ServerSocket.java, Compiled Code) at org.apache.catalina.core.StandardServer.await(StandardServer.java, Compiled Code) at org.apache.catalina.startup.Catalina.start(Catalina.java, Compiled Code) at org.apache.catalina.startup.Catalina.execute(Catalina.java, Compiled Code) at org.apache.catalina.startup.Catalina.process(Catalina.java, Compiled Code) at java.lang.reflect.Method.invoke(Native Method) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java, Compiled Code) Tomcat Logicals and Classpaths are cleared APACHE$WWW job terminated at 11-FEB-2008 15:55:48.63 Accounting information: Buffered I/O count: 39413360 Peak working set size: 62048 Direct I/O count: 1516596 Peak virtual size: 370784 Page faults: 13182 Mounted volumes:0 Charged CPU time:0 02:33:42.39 Elapsed time: 23 03:33:32.56 SY /snip - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Session expiration and AJAX issues
Hi, We've set our session expiration to 12 hours (I know it's long) and we're seeing behavior where certain browsers (namely IE) apparently can't count that high (we set the meta Refresh header but the page doesn't reload after the allotted time, session expiration time + 20 minutes). Are you saying that certain browser will never expire their sessions? Or are you saying that certain browsers kill their sessions before 12 hours (because they can't count that high)? Since this issue was discovered, we've added background AJAX timers on some of our web pages that refresh (authenticated) content. While this happily works, unfortunately, if the user chooses to remain on one of these pages, and then goes on vacation, the session stays active because the AJAX calls keep the session alive. The way I understand it - you are using ajax to keep a session alive. Why not set the session expiration to live as long as the browser is open, or for some other length of time? The session mechanism should work. I don't understand the need to hack sessions using ajax. it puts the onus on the browser to inform the server that the user's session needs to be expired. Isn't that part of the browser's job? - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Keep a Tomcat persistent SSL server connection
Dear folks, I have a long lived SSL connection which I'd like to maintain with the Tomcat server, but it times out after a few minutes. Can someone shed tips how to do maintain a long-lived SSL connection with a Tomcat server? Thanks ahead * http://RateMyBossCafe.com Leverage the Wisdom of Crowds * - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
