Thanks for your suggestion.
I added -XX:MaxPermSize=128m to JVM parameter and it seemed OK with my huge EJBs now!
Have you tried increasing the max permanent generation size ( e.g. used
for classes that are loaded) by setting -XX:MaxPermSize=128m
Something would have to be seriously wrong for Xmx1024m to be hit.
> I used -Xms128m -Xmx1024m for JVM parameters, will this work?
> I think I have about 100 EJBs, all are BMP beans.
> I have tried to cut down the size of XMLs by means of describing only
> one bean and it run quite well.
> Should it be the problem of XML parser?
> On 5/29/06, *Aaron Mulder* <firstname.lastname@example.org
> <mailto: email@example.com>> wrote:
> Have you tried increasing the JVM memory for Geronimo?
> How many EJBs do you have? And are you using CMP/CMR? I think it's
> safe to say we'd prefer not to get OOM errors in any case. :)
> On 5/28/06, Kevin <firstname.lastname@example.org <mailto:email@example.com>> wrote:
> > Hi All!
> > I have an entity bean jar that has an ejb-jar.xml of 317KB and an
> > openejb-jar.xml of similar size. When I start geronimo or
> redeploy this jar,
> > java.lang.OutOfMemoryError prompts sometimes. This jar is
> migrated from
> > JBoss and it was running all right on it.
> > Is there any solutions except dividing the jar into several parts?
> > Thanks and regards,
> > Kevin