Simon- something is happening to interfere with the successful completion of init() method of your Servlet such as cannot find classes such as 'uk.co.weft.exceptionhandler.BugzillaExceptionHandler' or one of the init-param in web.xml could be incorrectly spelled or not there put in log.debug or System,out.println() statements every other statement in your init method so you can see each line being executed in your init()
HTH, M-- --------------------------------------------------------------------------- This e-mail message (including attachments, if any) is intended for the use of the individual or entity to which it is addressed and may contain information that is privileged, proprietary , confidential and exempt from disclosure. If you are not the intended recipient, you are notified that any dissemination, distribution or copying of this communication is strictly prohibited. --------------------------------------------------------------------------- Le présent message électronique (y compris les pièces qui y sont annexées, le cas échéant) s'adresse au destinataire indiqué et peut contenir des renseignements de caractère privé ou confidentiel. Si vous n'êtes pas le destinataire de ce document, nous vous signalons qu'il est strictement interdit de le diffuser, de le distribuer ou de le reproduire. ----- Original Message ----- From: "Simon Brooke" <[EMAIL PROTECTED]> To: <users@tomcat.apache.org> Sent: Saturday, March 24, 2007 11:28 AM Subject: Marking servlet [] as unavailable, again... > Yes, I've read through previous threads on this subject; I haven't found > anything which helps me. > > Recently I've had a spate of unexplained 'Marking servlet [] as > unavailable' issues on my development server. It is a development > server, and so, of course, all the servlets on it are pretty much in > development; but the tomcat version is Debian's packaging of tomcat5, > package version 5.0.30-12, and has been installed 'out of the box' with > the only special configuration I've done to set > > JAVA_HOME=/opt/ibm-java2-i386-50 > TOMCAT5_SECURITY=no > > in /etc/default/tomcat5. No change has been made to the install since > 2006-05-15, and the 'Marking ... as unavailable' issue has only started > recently. > > what I'm getting in the localhost log is just: > > 2007-03-24 14:36:51 StandardContext[/pres]Marking servlet news as > unavailable > > What I'm getting in the catalina log is nothing relevant at all. My > webapp starts: > > 24-Mar-2007 14:36:27 org.apache.catalina.core.StandardHostDeployer > install > INFO: Installing web application at context path /pres from URL > file:/var/lib/tomcat5/webapps/pres > > Then my servlet starts to initialise itself: > > 24-Mar-2007 14:36:29 org.apache.catalina.startup.Catalina start > INFO: Server startup in 9479 ms > Will parse category article from pathinfo > Looking for class 'uk.co.weft.exceptionhandler.BugzillaExceptionHandler' > Looking for class 'uk.co.weft.pres.server.PrimitiveGenerator' > > And then - nothing at all. > > Nothing whatever is printed to catalina.out. > > I should say this does not affect the majority of my servlets; the > majority of the servlets in this webapp work perfectly. It's a minority > of servlets that are affected, and I suspect that the problem may be > dependency on Xerces; but without more diagnostics it's hard to be > certain. > > What I need to know is how to configure Tomcat so that it will print an > exception dump somewhere when it is marking things as unavailable. > > Thanks > > Simon > > -- > Simon Brooke :: [EMAIL PROTECTED] :: http://www.weft.co.uk/ > > Simon Brooke trading as The Web Engineering Factory and Toolworks. > > --------------------------------------------------------------------- > To start a new topic, e-mail: users@tomcat.apache.org > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
