I don't know how much memory the machine has. I have read various
articles on the net which have suggested increasing the memory
available to Tomcat's JVM (part of what Christoph suggested), but the
consensus seems to be that this merely defers the problem rather than
solving it. Memory leaks chew up memory until there is none left:
it's just a matter of how long it takes!
At the moment I'm concentrating on the JDBC hypothesis. If the
problem comes round again after that, there are two further
possibilities:
1) references (pointers) from outside the application to classes
within the application (non-JDBC)
2) memory size
I'm planning on taking them in that order. Although my instinct says
"fix the basic problem", if I only have to restart Tomcat say every
two weeks I may go with that if the solution proves too elusive.
Steve
On 21 Jul 2007, at 16:18, Jonathan Hipkiss wrote:
Do you know how much memory the machine has? We were getting this
on a Solaris 10 server with 1gb of Ram which we doubled and the
problem went away.
Jonathan
Stephen Winnall wrote:
Hi Antonio, Christoph
I'm using Cocoon 2.1.9 on Tomcat 5.5.23 with Sun's Java 1.5.0_11-
b03 on Linux 2.6.18-4-amd64 (not sure which distro: it's at my
provider's site).
Christoph's suggestions tally with things I've discovered on the
net in the last couple of hours. I'll run them past my provider.
Another possibility seems to be JDBC: if the jar file is under WEB-
INF/lib the garbage collector cannot release resources held by the
database. Guess where my postgresql.jar is...
Part of my problem is that I develop under Mac OS X and just
restart Tomcat when things go wrong in my development environment:
deploying to a completely different platform is forcing me to be
more rigorous.
Steve
On 20 Jul 2007, at 21:03, Antonio Gallardo wrote:
Hi Stephen, would you provide more info?
Java version, cocoon version, tomcat version, OS, etc?
Best Regards,
Antonio Gallardo.
Stephen Winnall escribió:
I'm trying to deploy my Cocoon application in Tomcat and am
getting the following error:
java.lang.OutOfMemoryError: PermGen space
Wisdom on the net has it that this happens as a result of large
memory leaks: if classes used in a servlet are referenced from
outside the servlet, the garbage collector cannot recycle them
when the application is undeployed; redeploying the application
results in the classes being loaded a further time, and so on
until memory runs out. I have looked in the Cocoon mailing lists
for other occurrences of this problem, but I've found nothing,
so I assume the problem is in one of the classes I wrote to
extend my application.
Does anyone have experience with tracking down this sort of
problem in Cocoon apps?
Steve
-------------------------------------------------------------------
--
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]
---------------------------------------------------------------------
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
