Re: Tomcat problems with large number of contexts in webapps

2008-06-13 Thread Filip Hanik - Dev Lists
if you use a more recent JDK, then the OutOfMemoryError should have an additional message, depending on what this message is, you'll need to apply different tuning parameters. so if you share the message with us, we can maybe help you, if your OOME doesn't have a message, upgrade your JDK and

RE: Tomcat problems with large number of contexts in webapps

2008-06-11 Thread Caldarale, Charles R
> From: mopont [mailto:[EMAIL PROTECTED] > Subject: Tomcat problems with large number of contexts in webapps > > we gave to tomcat -Xms 512m -Xmx1024m of memory, but we have > a "OutofMemory" even before reaching that limit. Need details here. What JDK are you using? I

Tomcat problems with large number of contexts in webapps

2008-06-11 Thread mopont
lar problem before? We already thinking in moving to SunAppServer... can someone here help me with this ? thanks in advance!!! -- View this message in context: http://www.nabble.com/Tomcat-problems-with-large-number-of-contexts-in-webapps-tp17788155p17788155.html Sent from the Tomcat - User mailing list archive at Nabble.com.

ImageMagick, tomcat problems.

2007-02-14 Thread aaron smith
I'm not a java developer, but one of our websites has a java backend. We just got a new version that has some major updates. It requires ImageMagick. I have installed ImageMagick and verifies it works with : convert logo: logo.gif, identify logo.gif, imdisplay logo.gif. I've also moved ImageMagick

Re: Detect tomcat problems with a custom java reporting apps?

2006-06-12 Thread Leon Rosenberg
---Ursprüngliche Nachricht- Von: Leon Rosenberg [mailto:[EMAIL PROTECTED] Gesendet: Montag, 12. Juni 2006 14:22 An: Tomcat Users List Betreff: Re: Detect tomcat problems with a custom java reporting apps? I'm not sure that after something "bad" happens you can access the server at all

AW: Detect tomcat problems with a custom java reporting apps?

2006-06-12 Thread Peter Neu
quent intervalls to see it bottle neck is ahead? I mean it's possible to define certain ranges. Any ideas? Cheers, Swen -Ursprüngliche Nachricht- Von: Leon Rosenberg [mailto:[EMAIL PROTECTED] Gesendet: Montag, 12. Juni 2006 14:22 An: Tomcat Users List Betreff: Re: Detect tomca

Re: Detect tomcat problems with a custom java reporting apps?

2006-06-12 Thread Leon Rosenberg
I'm not sure that after something "bad" happens you can access the server at all. An OutOfMemory or an AllThreadsBusy Exception normally lead to a non-responding tomcat. The best thing you could do is monitoring the logs with a separate script on the same machine and send mails on failure imho. r

AW: Detect tomcat problems with a custom java reporting apps?

2006-06-12 Thread Peter Neu
Yes, I am using this already. But there is some vital functionality missing. When an java.lang.outOf.MemoryException happens I won't get an alert unless I happen to be using lambda at the moment. So what we have at hand is a 'Schrödinger Cat' situation. I need to monitor the jmx control layer an

Re: Detect tomcat problems with a custom java reporting apps?

2006-06-12 Thread Leon Rosenberg
maybe you should look at existing tools first? http://www.lambdaprobe.org/d/index.htm regards leon On 6/12/06, Peter Neu <[EMAIL PROTECTED]> wrote: Hello, I want to build a small custom reporting tool for our tomcat production server. First of all is this the right place to ask about this ki

Detect tomcat problems with a custom java reporting apps?

2006-06-11 Thread Peter Neu
Hello, I want to build a small custom reporting tool for our tomcat production server. First of all is this the right place to ask about this kind of things or is this more a question for the dev list? The basic idea is, I want to send queries to tomcat and if one fails three times send out aler

Tomcat problems.

2006-02-15 Thread Angel Prieto
Hello, I'm having some problems with apache+tomcat with this configuration: Apache 2.0.51 (on Fedora Core 2) Tomcat 5.0.28 JDK 1.4.0_04 Mod_jk connector for FC2. Sometimes system goes down and we don't have any idea what the reason is. We get this error sometimes: 10-feb-2006 10:05:02 org.apa