That sounds similar to a problem that I had recently. Search the archives for messages with a subject of "JCL+Tomcat+Log4j related problems". Basically I was having problems because my JCL jars were too old.
On Apr 12, 2005 9:03 AM, Frank W. Zammetti <[EMAIL PROTECTED]> wrote: > Hi all, > > I'm having an odd little problem here... > > I have a webapp where I use Log4J underneath JCL. I use an XML config > file and Log4J is initialized in a ServletContextListener. The code in > the listener does some hackery on the XML... basically, I construct a real > path to my log files on the fly, update the XML and then configure logging > using the updated XML. Now, before anyone tells me how there are 10 other > and clearly better ways to do that (I have no doubt there are), the bottom > line is that this works and has worked for over a year. I've moved it > between Tomcat (on both Windows and Linux) and Websphere (and earlier > version) with no issue. > > The problem now though is that I'm deploying it on a newer Websphere > (5.1.1) on Windows... what's happening is that the log files are created > and are locked (i.e., I can't delete them), and they are where they are > supposed to be (a logs directory under my webapp), so everything SEEMS to > be starting up fine and as expected. However, no messages are making it > to the log files. They are showing up in Websphere's stdout and stderr > logs instead. So, I'm not sure this is a Log4J problem or strictly a > Websphere issue, but I'm hoping someone has seem a similar issue and can > shed some light on it. -- James Stauffer Are you good? Take the test at http://www.livingwaters.com/good/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
