I've had those errors with lifeCycle aswell, testing on orion I havent
had any problems except the occasional freeze that happens but I just go
into the console window and hit enter and it keeps working.
Rainer Hermanns wrote:
Yes, these were my expierences as well... Even with command line
sta
Yes, these were my expierences as well... Even with command line
startup, the same problem appears.
While deploying without reloading I do not get any OutOfMemoryErrors.
Since I start tomcat with mx512m there shouldn't be an issue with to
less memory right after startup.
Same problem appears wi
Francisco Hernandez wrote:
I've been getting this exception lately, I'm not sure if its
tomcat-4.1.24 thats messed up, webwork or something else, anyone else
having problems like these?
[snip]
root cause
java.lang.OutOfMemoryError
Apache Tomcat/4.1.24-LE-jdk14
You've run out of memory. You n
oading rather than restarting, just treat Tomcat like Windows and
restart several times a day.:)
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Pat Lightbody
Sent: Wednesday, August 20, 2003 8:40 AM
To: [EMAIL PROTECTED]
Subject: Re: [OS-webwork] webwork2
Sounds like your app is using too much memory. Have you tried profiling it
or giving it some more memory?
- Original Message -
From: "Francisco Hernandez" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, August 20, 2003 3:02 AM
Subject:
I've been getting this exception lately, I'm not sure if its
tomcat-4.1.24 thats messed up, webwork or something else, anyone else
having problems like these?
HTTP Status 500 -
type Exception report
message
description The server encountered an internal error () that prevented
it from fulfil
