You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by Martin van den Bemt <mv...@mvdb.com> on 2001/07/25 19:56:34 UTC

ehh small problem context/servlet reloading

Hi,

I use the latest version from cvs (not commits since my built..).
When compiling a new servlet, the system tries to remove the context and add
the context again (so far so good). I go the the servlet again and get :
Error: 503
Location: /servlet/cubic.adm.login
Application not available

each time I try to go there it will remove/add the context.

I can have a look at it (if you want) or maby someone can point into a
direction of where to look for this problem..

Mvgr,
Martin


RE: ehh small problem context/servlet reloading

Posted by Martin van den Bemt <mv...@mvdb.com>.
Me again with some more info on the issue below.
The following happens :
When I do a specific scenario of servlet access then replace a servlet and
start-up our login servlet I get the 503 error. The servlet has status 0 and
should have status 3 (according to my "debugging". All the other servlets
are still working (to a certain point, because most of them depend on the
servlet I am calling after the context is reloaded). I've been turning on
debugging, added my own logging etc,etc.. But still I cannot find where the
actual status of Request is set for that specific servlet, after the
reloading that is. Can someone please help me in where to exactly look for
this, because I cannot find it anymore. Didn't see anyone complain about
this problem yet, so I like to fix it ;-)). I'm using tc33 from cvs btw To
bad my debugger is horrible else it would be a little bit easier. Every
The problem doesn't occur when : I call servlet A go to B goto C replace B
and goto A again. (reloading is ok)
The problem occurs when : I call servlet A go to B goto C goto D replace B
and goto A again. (these are just my servlets, didn't test another scenario
yet, I first wanted to find the problem ;-)
Hope you guys can help to help me fix the bug and learn more about the
internals of tomcat..
TIA..

Here is some logging of the reloading (the strange logging is mine ;-).

2001-07-27 12:08:38 - ReloadInterceptor: MVDB : after removeing context
2001-07-27 12:08:38 - Ctx() : XXXXXXXXXXXXXXXXX CALLING CONTEXT SETSATE
XXXXXXXX
XXXXXXXXXX 0
2001-07-27 12:08:38 - Ctx() : XXXXXXXXXXXXXXXXX LEAVING SETCONTEXT
XXXXXXXXXXXXX
XXXX0
2001-07-27 12:08:38 - ContextManager: MVDB state ; 3 state_NEW 0
2001-07-27 12:08:38 - LogEvents: addContext DEFAULT:/ROOT
2001-07-27 12:08:38 - ReloadInterceptor: ADDCONTEXT in
ReloadInterceptorDEFAULT:
/ROOT
2001-07-27 12:08:38 - Ctx() : XXXXXXXXXXXXXXXXX CALLING CONTEXT SETSATE
XXXXXXXX
XXXXXXXXXX 0
2001-07-27 12:08:38 - Ctx() : XXXXXXXXXXXXXXXXX LEAVING SETCONTEXT
XXXXXXXXXXXXX
XXXX0
2001-07-27 12:08:38 - ContextManager: Adding context DEFAULT:/ROOT
2001-07-27 12:08:38 - ContextManager: after adding context the state is  : 1
2001-07-27 12:08:38 - ReloadInterceptor: MVDB: state after adding context..3
2001-07-27 12:08:38 - LogEvents: contextInit DEFAULT:/ROOT
2001-07-27 12:08:38 - SimpleMapper1: SM: extension map /*.jsp Ct (*.jsp  )
DependManager: Added /usr/local/tomcat33dev/webapps/cubic/WEB-INF/web.xml
web.xm
l
2001-07-27 12:08:38 - Ctx() : XXXXXXXXXXXXXXXXX CALLING CONTEXT SETSATE
XXXXXXXX
XXXXXXXXXX 1
2001-07-27 12:08:38 - Ctx() : XXXXXXXXXXXXXXXXX LEAVING SETCONTEXT
XXXXXXXXXXXXX
XXXX1
2001-07-27 12:08:38 - ReloadInterceptor: MVDB : status of contextmap : 0
class :
 org.apache.tomcat.modules.config.PathSetter
2001-07-27 12:08:38 - ReloadInterceptor: MVDB : status of contextmap : 0
class :
 org.apache.tomcat.modules.config.ServerXmlReader
2001-07-27 12:08:38 - LogEvents: contextMap R(  + /servlet/cubic.adm.login +
nul
l)
2001-07-27 12:08:38 - ReloadInterceptor: MVDB : status of contextmap : 0
class :
 org.apache.tomcat.modules.loggers.LogEvents
2001-07-27 12:08:38 - ContextManager: Host = swami.mvdb.com
2001-07-27 12:08:38 - ContextManager: SM: Prefix match
/servlet/cubic.adm.login
-> /servlet/cubic.adm.login/* ServletH cubic.adm.login(SW (null
CN=cubic.adm.log
in)) null
2001-07-27 12:08:38 - SimpleMapper1: Adjust for prefix map
/servlet/cubic.adm.lo
gin
2001-07-27 12:08:38 - SimpleMapper1: SM: After mapping R(  +
/servlet/cubic.adm.
login + null) ServletH cubic.adm.login(SW (null CN=cubic.adm.login))
2001-07-27 12:08:38 - ReloadInterceptor: MVDB : status of contextmap : 0
class :
 org.apache.tomcat.modules.mappers.SimpleMapper1
2001-07-27 12:08:38 - ContextManager: MVDB : showing servlet error


Mvgr,
Martin

> -----Original Message-----
> From: Martin van den Bemt [mailto:mvdb@mvdb.com]
> Sent: Wednesday, July 25, 2001 7:57 PM
> To: jakarta-tomcat-dev
> Subject: ehh small problem context/servlet reloading
>
>
> Hi,
>
> I use the latest version from cvs (not commits since my built..).
> When compiling a new servlet, the system tries to remove the
> context and add
> the context again (so far so good). I go the the servlet again and get :
> Error: 503
> Location: /servlet/cubic.adm.login
> Application not available
>
> each time I try to go there it will remove/add the context.
>
> I can have a look at it (if you want) or maby someone can point into a
> direction of where to look for this problem..
>
> Mvgr,
> Martin
>
>