Well this was odd. To me. I'm sure some of you will tell me about logging with Log4j or some other logger, or even the use of the Tomcat app manager.
My web.xml file got deleted. I thought, (probably wrongly) that Tomcat's web manager console would alert to such, but it didn't. Took me a little bit to discover that the darn thing was missing entirely! Ugh! Got that fixed, and many other ills like this logging thing resumed as they should! It's ALL working again! Thank you all! -----Original Message----- From: Christopher Schultz [mailto:ch...@christopherschultz.net] Sent: Monday, February 13, 2012 3:28 PM To: Tomcat Users List Subject: Re: Tomcat 6.0.26 stopped logging -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Barry, On 2/13/12 1:16 PM, Propes, Barry L wrote: > I am using Tomcat 6.0.26 on a few machines - Win XP Pro on two of > them, and Windows Server 2003 on the production machine. Also using > jdk1.6.0_18 and was on Ora10g, now 111g. That's quite an upgrade :) > Today, Tomcat stopped logging on two of the machines, and my servlet > that submits to the Oracle DB now fails. Fails in what way? Is an exception thrown? If so, what is the stack trace (or the message if no stack trace is generated)? > What is odd to me is that I use a Context object for connection on > this servlet, as well as a few other JSPs. > > The JSPs connect with no issue. The servlet fails. But either way, > would this upgrade inhibit Tomcat from logging? That seems strange to > me. Tomcat's logging should not have anything to do with the upgrade of your RDBMS. Did they upgrade anything else along with it? > My Context object is as follows. > > Context initCtx = new InitialContext(); Context envCtx = (Context) > initCtx.lookup("java:comp/env"); // Look up our data source DataSource > ds = (DataSource) envCtx.lookup("jdbc/myoracle"); // Allocate and use > a connection from the pool connection = ds.getConnection(); That looks fairly standard. Do you have the exact same code in both your JSPs (that work) and your servlets (that don't work)? Again, how do you know they don't work? Is there anything in the logs (hah) that suggests anything is amiss at any point? Funny things start to happen after an OOME, for instance. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk85gHkACgkQ9CaO5/Lv0PBolwCbBSzTpTgfXCHEcc2g/ZV0vr8l V68AoJB0vq32cuTvA4T9xlh/dmxyRzV3 =eTLa -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
