Re: Tomcat6.0.18+Log entries upon shutting down TomCat

2008-09-23 Thread Heiko Klein 

Hi Subhrajyoti,

I don't know an answer for your question, but I got exactly the same 
problems after upgrading from Tomcat 6.0.14 to 6.0.18. This problem 
happenend when using APR. After switching back to 6.0.14, my problem 
disappeared. Are you using APR, too? I think this is worrisome for an 
application, because my tomcat started to freeze completely after all 
threads had been in this 'waiting for deallocation' state.


Best regards,

Heiko

[EMAIL PROTECTED] wrote:

Hi All,
  My first question in this forum . I am load testing our 
webapp using Jmeter . The test was configured to simulate  50 simultaneous 
users . After running the test for about 18hours or so , I decided to 
shutdown Tomcat  and after executing shutdown.bat file , I got the 
following messages inside catalina.2008-09-23.log . At the time when I 
stopped Tomcat, Jmeter was showing as all the 50 threads up and running .

My question :

1. What this line INFO: Waiting for 253,020 instance(s) to be deallocated 
means ?

2. Are these messages worrisome from the application point of view ?
 .

Sep 23, 2008 1:53:38 PM org.apache.coyote.http11.Http11Protocol pause
INFO: Pausing Coyote HTTP/1.1 on http-8080
Sep 23, 2008 1:53:39 PM org.apache.catalina.core.StandardService stop
INFO: Stopping service Catalina
Sep 23, 2008 1:53:39 PM org.apache.catalina.core.StandardWrapper unload
INFO: Waiting for 253,020 instance(s) to be deallocated
Sep 23, 2008 1:53:40 PM org.apache.catalina.core.StandardWrapper unload
INFO: Waiting for 253,016 instance(s) to be deallocated
Sep 23, 2008 1:53:41 PM org.apache.catalina.core.StandardWrapper unload
INFO: Waiting for 253,015 instance(s) to be deallocated
Sep 23, 2008 1:53:41 PM org.apache.catalina.core.StandardWrapper unload
INFO: Waiting for 42 instance(s) to be deallocated
Sep 23, 2008 1:53:42 PM org.apache.catalina.core.StandardWrapper unload
INFO: Waiting for 42 instance(s) to be deallocated
Sep 23, 2008 1:53:43 PM org.apache.catalina.core.StandardWrapper unload
INFO: Waiting for 42 instance(s) to be deallocated
Sep 23, 2008 1:53:43 PM org.apache.catalina.core.StandardWrapper unload
INFO: Waiting for 7,570 instance(s) to be deallocated
Sep 23, 2008 1:53:44 PM org.apache.catalina.core.StandardWrapper unload
INFO: Waiting for 7,570 instance(s) to be deallocated
Sep 23, 2008 1:53:45 PM org.apache.catalina.core.StandardWrapper unload
INFO: Waiting for 7,570 instance(s) to be deallocated
Sep 23, 2008 1:53:53 PM org.apache.coyote.http11.Http11Protocol destroy
INFO: Stopping Coyote HTTP/1.1 on http-8080


Regards,

Subhrajyoti 
Mobile: +919830079545

Mail: [EMAIL PROTECTED]
Web: www.labware.com

LabWare LIMS Solutions - Results Count


-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Problems upgrading from 6.0.14 to 6.0.18

2008-09-22 Thread Heiko Klein 
Due to the announce security bug 
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-2938 I wanted to 
upgrade tomcat from 6.0.14 to 6.0.18.


Tomcat is running on a VPS on a Linux box with kernel 2.6.18. The 
application has been running for a while without any problems with 
tomcat 6.0.14. Load is difficult to measure due to invisible load on 
host-system.


After the upgrade, I got the following problems:

* running with the NIO http connector, tomcat crashed with a 'Too many 
open files' exception

java.io.IOException: Too many open files
at sun.nio.ch.ServerSocketChannelImpl.accept0(Native Method)
at sun.nio.ch.ServerSocketChannelImpl.accept(Unknown Source)
at 
org.apache.tomcat.util.net.NioEndpoint$Acceptor.run(NioEndpoint.java:

1163)
at java.lang.Thread.run(Unknown Source)


* running with the apr connector, tomcat crashed silently, even when 
shutting down it complained about threads it didn't managed to shut down.


* with apr and blocking http connector, I got problems with 
cookies-handling and the advise to use Base64 encoding for cookies.


After two month struggling to get tomcat in a stable state, I switched 
back to tomcat 6.0.14 with the original NIO connector:

Connector port=80
   protocol=org.apache.coyote.http11.Http11NioProtocol
   connectionTimeout=2
   URIEncoding=UTF-8
   compression=on
   enableLookups=false
   maxThreads=100
   maxSpareThreads=20 /
and everything worked without problems again. I made sure that I didn't 
use 'allowLinking' so I'm not in danger of the vulnerability.


I hope somebody has some ideas what has gone wrong. I would like to 
known what I should look for when upgrading the next time.


Best regards,

Heiko


-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Persistent session after browser restart, cookie expiration

2006-09-10 Thread Heiko Klein 

Hi,

I'm currently moving an web-application from custom-made to 
tomcat-servlet. Before, I used my own cookie management to store 
user-preferences. The cookies had a persistence on the browser of 1 
year, if the browser-configuration allowed that.


The default tomcat cookies for session-management seem to be deleted 
with browser-restart. How can I keep a session open even if the user 
restarts his computer? Or in other words, how can I set the 'Expires' 
field of the session-cookie send to the browser?


Best regards,

Heiko

-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]