I have had that already and it even may (and usually does) give the error at
the very first run. And there never is a permGen error in the log.
I am not sure but I am relating it with me moving the library jars out of the
project (to have a smaller .ear file) and adding these jars to the
It's a really bad idea to start randomly putting libs into the AS. Seam is
tested with everything packaged into the ear/war (you can just grab a clean
copy of your AS and put the ear in) - by following some other packaging
structure you loose the benefit of all that testing :( Follow the
Oops! All I meant was to speed up while developing. That turns into a different
subject now but please bear with me: I wish to know how you guys out there
handling this.
In the case I put things into the war/ear's lib I have a large file and that
slows down build-deploy-run cycle. Just because
I use exploded deployment as set up by seam-gen - this avoids the zip/unzip
time you mention and gives you the ability to change view files without a
restart. AFAIK seam-gen works with netbeans ootb
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4038395#4038395
Doing a lot of hot deploy? I usually find when things are screwy like this
there's a permgen memory error at the very bottom of that stack trace. A
restart of the app server causes the problem to go away.
I've recently migrated to JRocket R27.2 and haven't had any trouble so far.
JRocket
You can adjust the MaxPermSize by adding the following Java options:
-XX:PermSize=256m -XX:MaxPermSize=512
See the Getting Started chapter in the Seam documentation for more details.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4038195#4038195
Reply to the
