Getting java.lang.OutOfMemoryError: PermGen space
Hi,
In JCAPS5.1.1 after deploying my project, i am getting following error.
#|2007-02-20T16:38:48.319+0530|SEVERE|IS5.1.1|STC.eWay.batch.com.stc.connector. batchadapter.system.BatchInboundWork|_ThreadID=50; ThreadName=Worker: 140;stacktrace-id=13;|Exception in BatchInboundWork, BatchInboundWork terminated, e=java.lang.OutOfMemoryError: PermGen space
java.lang.OutOfMemoryError: PermGen space
|#]
Earlier also i have deployed projects but never
faced this type of error.
Please let me know Is there any work around to
rectify this kind of OutOf memory error.
Thanks
Venkatesh.S
Message was edited by:
VenkateshSampoornam
# 3
Thanks for replies.
Found additional information which most of people might aware of following information.
In JDK 1.5 there is support for getting warnings before these type of errors can occur.
java.lang.management package
For more information please look in to following link might be useful
1) http://www.theserverside.com/news/thread.tss?thread_id=27481
2) http://java.sun.com/j2se/1.5.0/docs/api/java/lang/management/MemoryMXBean.html
# 4
Hi Venkatesh,
It'll be interesting to find out if you get this OOM exception immediately when you deploy the project after you have booted the Integration Server, or if this problem occurs after repeatedly deploying/undeploying the application. The former points to a setting of -XX:MaxPermSize that is too low; the latter points to a memory leak.
I think that an incorrect setting of -XX:MaxPermSize is unlikely though because the setting is set to 128Mb by default already. Large OTDs do use a lot of space though.
If there's a memory leak, this may be caused by your specific application (see http://blogs.sun.com/fkieviet/entry/how_to_fix_the_dreaded). Of course it's also possible that there's a bug in CAPS. If you suspect the latter, make sure to contact support.
Frank Kieviet
http://blogs.sun.com/fkieviet
# 5
Hi Frank Kieviet,
Thanks for your reply.
The error occured due to repeated deploy/undeploy of project or
application.
After undeploying the project i restarted my logicalhost and repository
server. After this i didn't face the same problem. I don't know whether
restarting is the only (or) correct way, but as temporary solution i opted
for that.
I will try to reproduce the error, if the error persists i will contact
customer support.
Regards
Venkatesh.S
# 6
hi Venkatesh
I'm facing the same problem as you.i have contacted
customer support and provided them with dump files.
i found that it's related with the project.For example,project with jdbc will have this issue .
i can reproduce the error as the following step.
deploy a project which have jdbc operation>run it once>redeploy it.
repeat until the oom error occur.
To work around this problem,just restart logicalhost after having deployed many projects.
Regards
jett
2.28
