DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7026>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7026

AutoDeploy works bad

[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|WONTFIX                     |



------- Additional Comments From [EMAIL PROTECTED]  2002-03-12 14:40 -------
In my configuration file server.xml, I put :
<Http10Connector port="8080" secure="false" maxThreads="100" maxSpareThreads="10" 
minSpareThreads="4"/> 
<Ajp13Connector port="8009" maxThreads="100" maxSpareThreads="10" minSpareThreads="4"/>

But I still have the problem : when I update some times my web application, 
I have more and more native_threads java (corresponding of my application servlets 
which are loaded on startup).
(and the maxSpareThreads doesn't change anything)

So, I think there is a real bug.

But my question is :
Is there a solution, in tomcat 3.3, for updating existing web applications (on 
production servers) without re-starting the entire server ?

I tried with <AutoDeploy> (as described above) or with the Administration tools 
(remove then add context) 
but nothing is acceptable...

thanks

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to