tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Amy Roh <amy...@apache.org>
Subject Re: TC5 Servlet unavailable error
Date Wed, 02 Apr 2003 01:14:43 GMT


Costin Manolache wrote:
> Amy Roh wrote:
> 
> 
>>>Amy Roh wrote:
>>>
>>>
>>>>It seems like when context is stopped and restarted, servlet always
>>>>returns "unavailable".  You can generate an error by saving your
>>>>changes
>>>>in admin by "commit".  Then any process after that returns admin
>>>>servlet unavailalbe.
>>>>
>>>>Mar 31, 2003 4:48:29 PM org.apache.catalina.core.StandardWrapperValve
>>>>invoke INFO: Servlet admin.login_jsp is currently unavailable
>>>
>>>
>>>I tought I fixed it. Are you doing stop/destroy/init/start or just
>>>stop/start ?
>>
>>I'm not manually doing anything.  When I commit my changes in admin, I
>>think the admin context gets restarted and the application is set to
>>unavailable
>>right away.  Therefore any consequent requests fail.
> 
> 
> I'll try to fix it - probably moving the unregister/register from destroy
> to stop will do it.
> 
> Or maybe we can send a notification "context reloading" and have the mapper
> reset its data ?

I'm not sure.  Are you able to reproduce it?


> 
> Costin
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
> 



---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org


Mime
View raw message