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
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.
>> >
>> >
> 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.a
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
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.StandardWrapperValv