- This topic has 6 replies, 2 voices, and was last updated 19 years, 6 months ago by
.
-
Posts
-
I have myEclipse configured to start and stop weblogic 8. I often get the outOfMemory error in the weblogic console and the server stops responding.
Not sure if this matters, I have a project that is not in the MyEclipse structure, but I have custom ant scripts for the deployment and redeployment.
I start myeclipse with -Xms256M -Xmx512M and in the application server conifguration for weblogic 8, i have given -Xms128M -Xmx256M in the jvm arguments.
Any suggestions??
THanks,
Arun NArun,
you should also try to specify a max perm. size as well to your weblogic instance with -XX:MaxPermSize=… where the … should I would say be at least the size of all jar files loaded (weblogic.jar, jdbc, possibly wli related jars, and all your jar files).
E.g. we are having a big project where we use 196m as max. perm. size.
Regards,
Robert
Thanks Rob, Your suggestion seems to help. Playing around with the correct value for the setting. Will post my experience soon.
@robvarga wrote:
Arun,
you should also try to specify a max perm. size as well to your weblogic instance with -XX:MaxPermSize=… where the … should I would say be at least the size of all jar files loaded (weblogic.jar, jdbc, possibly wli related jars, and all your jar files).
E.g. we are having a big project where we use 196m as max. perm. size.
Regards,
Robert
Update: I had to raise it to 224m due to similar reasons… 🙂
Robert
The weird thing is that this does not happen always. it is only after the application has been redeployed a few times that i get this error. And this never happens when i run the server standalone(from the command prompt).. So now I am starting to wonder if this setting will help me.. if there is some memory leak when i start weblogic from thru eclipse, then the setting will probably delay this but dont think it will solve it.. anyway i am giving it a shot..
@arunpers wrote:
The weird thing is that this does not happen always. it is only after the application has been redeployed a few times that i get this error. And this never happens when i run the server standalone(from the command prompt).. So now I am starting to wonder if this setting will help me.. if there is some memory leak when i start weblogic from thru eclipse, then the setting will probably delay this but dont think it will solve it.. anyway i am giving it a shot..
There is a memory leak up to at least 8.1SP3 (maybe even SP4 as well) during deployment, that is for sure.
We are not able to deploy even our ejb jar containing the entities twice during one running of the server. When you first deploy the jar from the console, it deploys without a problem. However when you try to do it a second time (first deleting it from the console, then deplyoing again as if from scratch), it reliably fails with OutOfMemory. We do not even need to run code on any of the ejbs, just deploy the jar file containing only entities, and session beans, and no startup classes. (the jar file is 45 megs)
So there definitely is a memory leak somewhere in the classloaders in WLS 8.1SP3, probably earlier classloaders are not properly discarded on undeploy.
Regards,
Robert
