[Bug 251004] Re: Tomcat 5.5 produces no logs when run with gcj

2009-02-24 Thread Thierry Carrez
Yes. Absence of logs is only the first of the problems you'll encounter if you use gcj to run Tomcat :) ** Changed in: tomcat5.5 (Ubuntu) Status: New = Won't Fix -- Tomcat 5.5 produces no logs when run with gcj https://bugs.launchpad.net/bugs/251004 You received this bug notification

[Bug 251004] Re: Tomcat 5.5 produces no logs when run with gcj

2009-02-23 Thread Tom Haddon
I actually switched to using sun-java6-jdk but will try openjdk. Just wanted to report the bug in any case, but it sounds like we'd mark it as Won't Fix? -- Tomcat 5.5 produces no logs when run with gcj https://bugs.launchpad.net/bugs/251004 You received this bug notification because you are a

[Bug 251004] Re: Tomcat 5.5 produces no logs when run with gcj

2009-02-16 Thread Thierry Carrez
Tomcat isn't really working well with the GCJ jvm... Any reason why you wouldn't run with OpenJDK ? Now that bug 212521 has been fixed in hardy you can easily use it with Tomcat 5.5... It works as advertised, and also is so much faster... -- Tomcat 5.5 produces no logs when run with gcj

[Bug 251004] Re: Tomcat 5.5 produces no logs when run with gcj

2009-02-11 Thread Tom Haddon
I'm actually seeing some logging - it's going to /var/log/syslog instead of into /var/log/tomcat5.5, fwiw. Sample ps output shows SYSLOG: mthad...@gpsdb-jasperserver:~$ ps auwxx | grep tomcat | grep -v grep root 11332 0.0 0.0 2064 356 ?Ss 06:36 0:00 /usr/bin/jsvc -user

[Bug 251004] Re: Tomcat 5.5 produces no logs when run with gcj

2009-02-10 Thread Tom Haddon
I can confirm I have the same issue, and changing /etc/default/tomcat5.5 to show TOMCAT5_SECURITY=no doesn't make the logs appear. ** Changed in: tomcat5.5 (Ubuntu) Status: Invalid = New -- Tomcat 5.5 produces no logs when run with gcj https://bugs.launchpad.net/bugs/251004 You received

[Bug 251004] Re: Tomcat 5.5 produces no logs when run with gcj

2008-12-05 Thread Thierry Carrez
We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comment. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on