another potential solution is to try a different JVM like Bea's JRockit. JRockit provides some built in profiling capabilities, so that is another way to get some profile data quickly.
peter On 2/28/06, Tim Lucia <[EMAIL PROTECTED]> wrote: > > I use JProfiler with Tomcat all the time. > > -----Original Message----- > From: news [mailto:[EMAIL PROTECTED] On Behalf Of Tomasz Nowak > Sent: Tuesday, February 28, 2006 6:37 PM > To: users@tomcat.apache.org > Subject: Re: Sad: Tomcat 5.5.x crashes almost every single day. > > Remy Maucherat <[EMAIL PROTECTED]> wrote: > > > > In case you haven't noticed, it is extremely hard to do, because > > webapps have their own logging mechanism most of the time. You mention > > the logger element of 4.x, but it didn't actually do anything (it did > > put the internal logging for the specified container, as well as the > > logging done using the ServletContext - aka, the ugliest and most > > useless logging facility ever). > > Tomcat 5.5.15 and j.u.l use hierarchical categories for the containers > > so that you can easily replicate the logging that was done by the > > logger element. The default logging.properties does that for > > "localhost". I do not consider logging.properties to be poor or bad in > > any way. > > Hm. Here is my logging.properties: > http://www.biochip.pl/logging.properties.txt > The way new vhosts are added is pretty stupid for me but > lets forget about the semantics now. > > I've added swallowOutput attibute to serveral context. > How should it suppose to work? On my box it works in this way: > - The only file that actually logs anything that matters is catalina.out > - Most of catalina.out inputs also appear in localhost.timstamp.log > - Nothing more then manager actions are logged to vhost logs > - After tomcat has stared, the only input logs are: > > a) useless: > INFO: Response already committed > Feb 28, 2006 10:59:22 PM org.apache.jk.core.MsgContext action > INFO: Response already committed > Feb 28, 2006 10:59:22 PM org.apache.jk.core.MsgContext action > INFO: Response already committed > Feb 28, 2006 10:59:22 PM org.apache.jk.core.MsgContext action > INFO: Response already committed > Feb 28, 2006 10:59:22 PM org.apache.jk.core.MsgContext action > INFO: Response already committed > Feb 28, 2006 10:59:22 PM org.apache.jk.core.MsgContext action > (repeted serveral times every single minute (!) on my machine) > > b) sth like: > Feb 28, 2006 11:00:03 PM org.apache.jk.core.MsgContext action > WARNING: Error sending end packet > java.net.SocketException: Broken pipe > at java.net.SocketOutputStream.socketWrite0(Native Method) > at > java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) > at > java.net.SocketOutputStream.write(SocketOutputStream.java:136) > at > org.apache.jk.common.ChannelSocket.send(ChannelSocket.java:518) > at > org.apache.jk.common.JkInputStream.endMessage(JkInputStream.java:112) > at org.apache.jk.core.MsgContext.action(MsgContext.java:293) > > So how can I: > - configure it to work similary to tomcat 4.1, I mean > logs from different vhost go to different files > - configure Tomcat not to log anything that belongs to vhost > to catalina.out > - turn of these useless jk infos > > PS. > Tim Lucia: I don't care about access logs, HTTPd logis it for me. > > > Right, you want an integrated profiler, ready to enable, and with no > > performance cost. I'd like to have it too. > > OK, so what is the easiest to implement and easiest use to profiler > that I can use with Tomcat? > > > It depends, on some OSes, it's apparently impossible to get a threaded > > server to run properly indeed. You're using Linux 2.4.something. Try > > updating to 2.6. If you are using Redhat or another Redhat based > > distros, always use LD_ASSUME_KERNEL. > > Is Tomcat on 2.6 so called "thread save"? > > I've come over several warnings about Apache httpd 2.0 > in 'threaded' mode on Linux kernels. People (also PHP dev's) > seem to recommend sticking with 1.3. > > -- > T. > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
