Application Manager 8 have options to monitor various servers including JBoss server, but, for JBoss 5.0.1, I could not add a monitor easily. Telling long story in short, it is a 2 minute task if you have the correct way to do so (however I spent about a day to google for the solution and testing). So, here is the correct way:
- Start JBoss server on a particular IP address by passing the “-b a.b.c.d” argument, where a.b.c.d is the IP address in dotted decimal notation, like 172.16.4.111 .
In Componence, we use a custom script to do that, i.e. runStandalone.sh or runCluster.sh; so, I updated that one.
- Restart the JBoss server and try to add the monitor again, and it works.
But, you may not be able to monitor the JVM information yet. But don’t worry, this is also a 2 minute task to rectify the problem. Just
- Copy the $APPMAN_HOME/working/resources/jbossagent.sar to the deploy directory of the running server so that it got hot deployed.
JVM information, max heap size and current heap size is now available.
When you start Jboss 5.x server, by default it will bind to localhost ( i think this was done since Jboss 4.2 ). Applications manager will try to connect to the jboss server using hostname and this will result in error. Hence if you start your jboss server by using -b 0.0.0.0 option or -b option or -b option, applications manager can connect with the jboss.
Applications Manager will automatically deploy a Mbean ( jbossagent.sar ) in your jboss server using jboss.system:service=MainDeployer’s deploy method ( we will provide the jbossagent.sar file’s http url -> http://appmanager:port/resources/jbossagent.sar as input to this method ). However this method has been changed in jboss 5 and it is no longer accepting http urls as input. So the jbossagent.sar file is not getting deployed automatically for Jboss 5.x server. So you should manually deploy the jbossagent.sar file in jboss server by copying this file into deploy directory of your jboss server.
There has been architecture changes in jboss 5.x which will result in some exception being thrown when you deploy the jbossagent.sar file bundled with present version of applications manager ( versions 8.x ). We will fix this problem in applications manager 9. For now you can download the jbossagent.sar file from this URL http://demo.appmanager.com/jbossagent.sar and deploy this sar file in your jboss. To deploy this new jbossagent.sar file follow the below steps :
1. Stop your jboss and remove the old jbossagent.sar file from deploy directory
2. Start your jboss server. Once jboss has completely started, copy the new jbossagent.sar file to deploy directory of jboss
3. Restart applications manager
This will give you all metrics from your jboss monitor in applications manager.
- Arun
I don’t know the key to success, but the key to failure is trying to please everybody.