Sorry, I never looked at the subject line.
I suggest you also set -Xms1300m. This will set the min and max heap to the same size (as it is, you are probably getting an initial heap of 64m, with the JVM constantly asking the OS for more). This will also prevent you from getting "out of memory" errors if the JVM asks the OS for more memory and the OS refuses to allocate it.
Also, try running with -verbose:gc set, this should show you the amounts of heap in use before and after each garbage collection. Relying on the OS to tell you about the JVMs memeory usage is usually not too helpful.
Also, I hope that you have at least 2GB of RAM on your machine. Otherwise you might not be able to get a 1.3GB heap.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4118799#4118799
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4118799
Hi Tim,
This issue is causing me serious problems. I am seeing my application sieze up completely for a full minute while the JVM runs a full GC, and even the minor GCs are seriously reducing throughput.
Perhaps if you could help me understand under what circumstances the call chain MessagingXAResource.end -> MessagingXAResource.unsetCurrentTransactionId -> ResourceManager.createLocalTx might be executed, I could take a stab and patching this myself and contribute my findings back to you.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4118797#4118797
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4118797
JBossAS 5.0 beta3 has changed the scoping of classes within war files. Previously (as in 4.x.x, and even in beta3 as of last September), if a class in some other archive (such as an ear) attempted to instantiate a class packaged in a war, I got a exception. With beta3 (and beta4 pulled today after Adrian's classloader change - JBAS-5119), the class is successfully instantiated.
At first I thought that the "useJBossWebLoader" property might now default to true, but is is still false.
Is this new behavior intended, or are the new class loaders broke?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4118795#4118795
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4118795