I'm running out of memory with the msg:
...
WARNING: Error registering request
May 25, 2004 5:36:44 PM
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable run
SEVERE: Caught exception (java.lang.OutOfMemoryError) executing
[EMAIL PROTECTED], terminating thread
May 25, 2004 5:37:05 PM org.ap
Hello Robert,
We are having the same problem with mod_jk 1.2.5 and Tomcat 5.0.19.
However, we cannot downgrade to Tomcat 5.0.18 because of a bug fix
regarding session states. I was wondering, have you guys tried
disableing the JMX registration? Was that indeed the problem?
Thank you very mu
I know, I ran a few hundred lynx's at a time.
Ralph Einfeldt wrote:
To your question: I don't know.
Having a delay in the jsp (or servlet) isn't enough to
enshure concurrent requests. You have to do something
on the calling site to enforce this.
If you just call lynx as in your example, lynx wi
]
> Sent: Friday, March 19, 2004 7:21 PM
> To: Tomcat Users List
> Subject: Re: Horrible memory leak in tomcat 5.0.19 (JMX bug?)
>
> Why are those message generated by a thread starting up or something?
> If so I already have a jsp with a built in delay I can use to
> make sure
Robert Krüger wrote:
Hi,
we had the same problem (enormous memory leak which frequently made our
production system crash), downgraded to 5.0.18 and everything went back
to normal. Just yesterday a colleague of mine came to the conclusion
that it is not too unlikely that it is the problem descri
Ralph Einfeldt wrote:
That may be a bit to simple, as this is just performing one
request after the other. You may have to force concurrent
request:
Why are those message generated by a thread starting up or something?
If so I already have a jsp with a built in delay I can use to make sure
the
o start.)
> -Original Message-
> From: Joseph Shraibman [mailto:[EMAIL PROTECTED]
> Sent: Thursday, March 18, 2004 8:32 PM
> To: Tomcat Users List
> Subject: Re: Horrible memory leak in tomcat 5.0.19 (JMX bug?)
>
>
> My test to try to reproduce this bug was:
> i=1
> while
So how do I reproduce these messages:
Mar 18, 2004 2:33:31 PM org.apache.jk.common.HandlerRequest invoke
INFO: Unknown message 0
Mar 18, 2004 2:46:46 PM org.apache.jk.common.HandlerRequest decodeRequest
WARNING: Error registering request
... which presumably are related to the memory leak?
Shapir
Hi,
>What is this JMX thing anyway? Is it supposed to produce a report for
>the jk status page (that I could never get to work anyway?)
It's a lot more than that: many tomcat components are now manageable via
JMX (any JMX console will do). There's also a nice report in the
Manager webapp (http
Great, thanks for the info! But I already downgraded my production
machine to 4.1.18 to avoid this problem. I wish I knew how to reproduce
this on my development box so I can know for sure if this solves the
problem. Otherwise I can't justify trying this in productions.
My test to try to rep
Hi,
we had the same problem (enormous memory leak which frequently made our
production system crash), downgraded to 5.0.18 and everything went back
to normal. Just yesterday a colleague of mine came to the conclusion
that it is not too unlikely that it is the problem described in the message
h
Shapira, Yoav wrote:
Hi,
Does the memory leak occur when you run tomcat standalone?
I can't run the production server in standalone, and I can't seem to hit
my test server hard enough to reproduce the problem clearly. I'll keep
trying.
Can you
point out its source e.g. by running with a profi
mailto:[EMAIL PROTECTED]
>Sent: Wednesday, March 17, 2004 1:55 PM
>To: Tomcat Users List
>Subject: Horrible memory leak in tomcat 5.0.19
>
>I recently upgraded my production server from jk 1.2.5/tomcat 4.1.18 to
>jk 2.0.2/tomcat 5.0.19. I'm having a horrible memory leak no
I recently upgraded my production server from jk 1.2.5/tomcat 4.1.18 to
jk 2.0.2/tomcat 5.0.19. I'm having a horrible memory leak now and need
to restart tomcat frequently when it runs out of memory. I always had
set the max memory to 512m, now after running around 50 minutes memory
usage is
14 matches
Mail list logo