<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	>
<channel>
	<title>Comments on: Configuring JBoss server monitoring in ManageEngine AM</title>
	<atom:link href="http://blog.componence.com/2009/04/08/configuring-jboss-server-monitoring-in-manageengine-am/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.componence.com/2009/04/08/configuring-jboss-server-monitoring-in-manageengine-am/</link>
	<description>Your Portal, Our Business</description>
	<pubDate>Fri, 30 Jul 2010 00:38:26 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Si</title>
		<link>http://blog.componence.com/2009/04/08/configuring-jboss-server-monitoring-in-manageengine-am/comment-page-1/#comment-2701</link>
		<dc:creator>Si</dc:creator>
		<pubDate>Mon, 23 Nov 2009 12:16:20 +0000</pubDate>
		<guid isPermaLink="false">http://blog.componence.com/?p=74#comment-2701</guid>
		<description>I don't know the key to success, but the key to failure is trying to please everybody.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t know the key to success, but the key to failure is trying to please everybody.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Arun</title>
		<link>http://blog.componence.com/2009/04/08/configuring-jboss-server-monitoring-in-manageengine-am/comment-page-1/#comment-7</link>
		<dc:creator>Arun</dc:creator>
		<pubDate>Thu, 09 Apr 2009 08:56:35 +0000</pubDate>
		<guid isPermaLink="false">http://blog.componence.com/?p=74#comment-7</guid>
		<description>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 -&gt; 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</description>
		<content:encoded><![CDATA[<p>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.</p>
<p>Applications Manager will automatically deploy a Mbean ( jbossagent.sar ) in your jboss server using jboss.system:service=MainDeployer&#8217;s deploy  method ( we will provide the jbossagent.sar file&#8217;s http url -&gt; <a href="http://appmanager:port/resources/jbossagent.sar" rel="nofollow">http://appmanager:port/resources/jbossagent.sar</a> 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.</p>
<p>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 <a href="http://demo.appmanager.com/jbossagent.sar" rel="nofollow">http://demo.appmanager.com/jbossagent.sar</a> and deploy this sar file in your jboss. To deploy this new jbossagent.sar file follow the below steps :<br />
1. Stop your jboss and remove the old jbossagent.sar file from deploy directory<br />
2. Start your jboss server. Once jboss has completely started, copy the new jbossagent.sar file to deploy directory of jboss<br />
3. Restart applications manager<br />
This will give you all metrics from your jboss monitor in applications manager. </p>
<p>- Arun</p>
]]></content:encoded>
	</item>
</channel>
</rss>

