Hi,
When i done migration to Seam 1.2 i saw when i deploy 2 or 3 times app i get serwer error "pergem space" out of memory and neet to shot down whole serwer.
But when i used Seam 1.0.0 i could deploy much more times app.
Is this normal, when seam grows so quicly i'll be restart server for each deploy. I get thinking Seam is gettin to much heavy...
I changed run.bat properties to 256mb but this doesn't helped, so what should i do ?
| set JAVA_OPTS=%JAVA_OPTS% -Xms256m -Xmx512m -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000
|
I use Seam 1.2.0 Path1, Drools,
By the way sould it be so much jars for drools?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4033295#4033295
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4033295
"gavin.king(a)jboss.com" wrote : There is no good, standards-compliant, way to pass a conversation id transparently over RMI. Even if there was, the semantics are questionable, since conversation state is local, not remotely accessible.
|
| For WS, the notion of a conversation is better-defined.
I´m a bit confused...
What I want to know is if I can use a Statefull Session Beans Seam Component colled remotly by an swing application (via a command handler)...
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4033291#4033291
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4033291