Re: Tomcat Crashes after 1000 sessions.

Vikram Godse <[EMAIL PROTECTED]> wrote: > > Hi, > My CATALINA_OPTS parameter has the following values i have 4gb ram on > my server > > > CATALINA_OPTS="-server -XX:MaxPermSize=512m -Xms1024m -Xmx1024m" > > This is what i see in the tomcat manager server info. > > Max threads: 200 Min spare threads

Re: "Response already committed" when redirecting from error page?

David C. Schweisguth <[EMAIL PROTECTED]> wrote: > > Mar 2, 2006 2:15:47 PM org.apache.jk.core.MsgContext action > INFO: Response already committed I have a lot of these every single mintue, and I'm not redirecting any error pages, just making a header location stuff. See my recent posts. -- T.

Re: Sad: Tomcat 5.5.x crashes almost every single day.

Peter Lin <[EMAIL PROTECTED]> wrote: > > honestly, I really doubt logging will produce anything useful beyond > the VM dump you already posted. My first hand experience, the logs > won't help at this point. What needs to happen is to step through the > code and see exactly what is happening. > > i

Re: Sad: Tomcat 5.5.x crashes almost every single day.

Filip Hanik - Dev Lists <[EMAIL PROTECTED]> wrote: > > This could be completely unrelated, but let me throw something at you, > maybe it will help > btw. I prefer to run mod_proxy over mod_jk over http, much simpler, > and > in *our* load tests has scaled much better during stress. > > >Response a

Re: Sad: Tomcat 5.5.x crashes almost every single day.

Peter Lin <[EMAIL PROTECTED]> wrote: > > my advice is dive in and try to debug it, or hire someone with > experience debugging webapps. > > there's no much others can do for you at this point, since it's > debugging. good luck. I've just meant configuring the logging system: > > > So how can I:

Re: Sad: Tomcat 5.5.x crashes almost every single day.

Tomasz Nowak <[EMAIL PROTECTED]> wrote: > > 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 t

Re: Sad: Tomcat 5.5.x crashes almost every single day.

Peter Lin <[EMAIL PROTECTED]> wrote: > > 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. I've read about jrockit 5.0 SP1. They say it has a new feature that

Re: Sad: Tomcat 5.5.x crashes almost every single day.

Wade Chandler <[EMAIL PROTECTED]> wrote: > > Sometimes changing the ratio to not have enough new > space and then creating too many objects too fast can > make your application eventually throw OOMEs because > it can't move the objects into older spaces quick > enough depending on what you applicat

Re: Sad: Tomcat 5.5.x crashes almost every single day.

Nathan Smith <[EMAIL PROTECTED]> wrote: > > The problem can be fixed by increasing your -XX:MaxPermSize value to > more than 256. I've increased it to 512m now. I'll see. > Download and use a program called visualgc available here > http://java.sun.com/performance/jvmstat. You can have it running

Re: Sad: Tomcat 5.5.x crashes almost every single day.

Peter Lin <[EMAIL PROTECTED]> wrote: > > It's not at all clear why -XX:MaxPermSize=256m isn't working and the > perm size is still at the default. If the perm gen was set correctly, > wouldn't the dump show something other than 99%? You're right, it shows PSPermGen total 50304K not the 256

Re: Sad: Tomcat 5.5.x crashes almost every single day.

Peter Lin <[EMAIL PROTECTED]> wrote: > > look at the dump, it looks like the permgen ran out of space > > PSPermGen total 50304K, used 50170K [0x445f, 0x4771, > 0x545f) > object space 50304K, 99% used [0x445f,0x476ee878,0x4771) > > try increasing your permGen to 128Mb

Re: Sad: Tomcat 5.5.x crashes almost every single day.

Leon Rosenberg <[EMAIL PROTECTED]> wrote: > > kill -SIGQUIT (i think its kill -11) your tomcat-java process Ok, it has happened again ! Simply: Mar 1, 2006 2:28:34 AM org.apache.catalina.connector.CoyoteAdapter service SEVERE: An exception or error occurred in the container during the request pro

Re: Sad: Tomcat 5.5.x crashes almost every single day.

Leon Rosenberg <[EMAIL PROTECTED]> wrote: > > you should seriously consider upgrading to 2.6.x linux. 2.4.s thread > support simply sucks! If your tomcat spawns more than allowed threads > it will get an outofmemoryerror and simply die... And I don't mean > your 200 tomcat httpworker threads only,

Re: Sad: Tomcat 5.5.x crashes almost every single day.

Tim Lucia <[EMAIL PROTECTED]> wrote: > > #2 - Do any commercial application server vendors offer you > assistance on how to find bugs in application code? You're much more > likely to find these answers using google, or reading wikis or from > community support. There are hundreds of such discuss

Re: Sad: Tomcat 5.5.x crashes almost every single day.

Leon Rosenberg <[EMAIL PROTECTED]> wrote: > > We had some serious problems with tomcat, which are solved now, > however, we are on 5.0.25 (with session patch) and not on 5.5.x yet. > However, when tomcat dies, what your cpu usage is looking like? 100%? I've noticed that when tomcat hangs - load av

Re: Sad: Tomcat 5.5.x crashes almost every single day.

Nathan Smith <[EMAIL PROTECTED]> wrote: > > Hi Tomasz, > > you mentioned below that you have a MaxPermSize of 256m. I have not seen "OOME: PermGen" errors on that machine but after having some of them on other machine with aditonal 10 webapps deployed I've increased it from default 64m to 256m to

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 specifie

Re: Sad: Tomcat 5.5.x crashes almost every single day.

Tim Lucia <[EMAIL PROTECTED]> wrote: > > Send Tomcat a QUIT (11) signal on Unix, or control/break (run it > interactively) on Windows. This will cause the VM to dump all thread > stacks. > > If you don't like Tomcat, you can always shell out some big bugs for a > commercial application server. Fo

Re: Tomcat 5.5.x crashes almost every single day.

John C. Dale <[EMAIL PROTECTED]> wrote: > > PHP is great. So is Zoap and .NET. Careful, though, some of the same > problems you would be shunning Java for would also appear in any > Internet development/application development platform. I know the pitfalls of PHP, I been developing php webapps b

Re: Sad: Tomcat 5.5.x crashes almost every single day.

Peter Crowther <[EMAIL PROTECTED]> wrote: > > Have you tested it for deadlocks that would cause hangs? > [...] Profile your application. What's eating memory? > Get a thread dump when your application hangs. Is anything > deadlocked? What? Where? How? http://www.google.com/search?hl=pl&q=%22th

Re: Tomcat 5.5.x crashes almost every single day.

#x27;ve browsed the JMX management manual.. well is it written for a human being? Looks like a "finish it yourself" thing. :| -- Tomasz Nowak Netventure, http://www.netventure.pl/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: Sad: Tomcat 5.5.x crashes almost every single day.

Mark Eggers <[EMAIL PROTECTED]> wrote: > > > enableLookups="true" redirectPort="8443" /> > > Why enableLookups="true" ??? I use request.getRemoteHost in couple of places. > Also, Cocoon can be very resource-intensive depending > on which blocks you've built. Almost always only: - databases-

Sad: Tomcat 5.5.x crashes almost every single day.

Probably important: === - 2x Xeon, 3 GB mem - Linux 2.4.26 - Java 1.5.0_06-b05 - Apache Tomcat 5.5.15 - CATALINA_OPTS="\ -server \ -Djava.awt.headless=true \ -Dfile.encoding=UTF-8 \ -XX:MaxPermSize=256m \ -Xms1024m -Xmx1024m" - - mod_jk 1.2.15 - Apache Httpd 1.