Wednesday April 02, 2008
GlassFish v2: Changing JVM Options in a Cluster Config - make sure you start the instances properly
I recently came across an issue where I had to set particular jvm options like; the system classpath, the javaagent, a log4j reference etc.
When starting the node-agent with the default operation of starting the listening instances (instances syncing with that particular node-agent) asadmin start-node-agent NODE-AGENT-NAME I was seeing that the newly inputted configurations were not getting synchronized with the cluster-configuration changes.
After discussing with engineering I found out it was a known problem with the start-up sequence and that the workaround was to start the node-agent without the instances starting as well. Then after a successful node agent start I would/can then start the cluster (the instances).
The commands I used to do this was/were:
1) asadmin start-node-agent --startinstances=false NODE-AGENT-NAME
2) asadmin start-cluster CLUSTER-NAME
After following these two steps above as oppose to the default node-agent start fixed the issue. I got my JVM settings down to the instances... I also wrote a wiki entry on this issue here http://wiki.glassfish.java.net/Wiki.jsp?page=JVMOptions
Posted at 03:04PM Apr 02, 2008 by Chris Fleischmann in GlassFish | Comments[0]
This is a personal weblog, I do not speak for my employer.