I did not go into detail earlier as I did not seem relevant.. but just FYI ... The original problem was on Tomcat 4.1.29.. I never use the bleeding edge versions but download what "at that time" was indicated as the best "stable build" On my Windows dev machine I have 4.1.18 and since it behaved the same I did not think that upgrading it at that point would be any help..
Your points on installers are understood, I just never had any problems with them so it did not seem a issue. Also I NEVER put anything in the Program Files directory.. and I rarely use any MS products so nuking that directory would not have been noticed..<G> (actually I only use Windows when a client requires it, my real machines are Linux and MacOSX..)
I'm working on moving from the simple case to the original app and hope I can track down what mucked things up.. I'll post my results later...
John..
Jacob Kjome wrote:
I'm really not sure. You can try and do as I suggest above and not use the installer (and maybe move to a version of Tomcat that is actually current. 4.1.18 is ancient. Heck, 5.0.18 is out already... and quite stabe, if you as me). First I suggest you get System.out.println() to show up. Until this works, I can't see how you can begin to figure out how this relates to Log4j. I recommend sending a message to the Tomcat-user list about this.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
