Support Migration Notice: To update migrated JIRA cases click here to open a new case use www.vmware.com/go/sr | vFabric Hyperic 5.7.0 is Now Available

Hyperic HQ

JBoss plugin - control action start does not complete and reports error

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Deferred
  • Affects Version/s: 4.5, 4.5.1
  • Fix Version/s: None
  • Component/s: Plugins
  • Environment:
    HQ-server 4.5.0.1-EE-10 running on RHEL 5.4
    HQ-agent 4.5.0.1-EE-10 running on RHEL 5.4
     - JBoss 5.0.1 running with HQ-agent
  • Case Links:
    none
  • Regression:
    No

Description

JBoss plugin - control action start does not complete and reports error.

When attempting to start a stopped JBoss from the Control Actions, the operation times out and reports:

Control Action: start Description:
Command State: Error
Date Started: 11/12/2010 12:35 PM
Command Status: er Temp Dir: /opt/jboss/jboss-5.0.1.GA/server/default/tmp 12:35:08,068 INFO [ServerImpl] Server Temp Deploy Dir: /opt/jboss/jboss-5.0.1.GA/server/default/tmp/deploy 12:35:08,717 INFO [ServerImpl] Starting Microcontainer, bootstrapURL=file:/opt/jboss/jboss-5.0.1.GA/server/default/conf/bootstrap.xml 12:35:09,350 INFO [VFSCacheFactory] Initializing VFSCache [org.jboss.virtual.plugins.cache.CombinedVFSCache] 12:35:09,353 INFO [VFSCacheFactory] Using VFSCache [CombinedVFSCache[real-cache: null]]
Date Scheduled: 11/12/2010 12:35 PM
Elapsed Time: 00:10:02.199

This is a different error than reported from executing the control action restart.

The agent.log reports:

2010-11-12 12:45:09,915 DEBUG [Thread-0] [MeasurementCommandsService] Error getting real time measurement 'jboss:service=TransactionManager:RollbackCount:java.naming.provider.url=jnp%3A//vmc-ssrc-rh135%3A1099,java.naming.security.principal=%java.naming.security.principal%,java.naming.security.credentials=': Error retrieving value: Can't connect to MBeanServer [java.naming.provider.url=jnp%3A//vmc-ssrc-rh135%3A1099,java.naming.security.principal=%java.naming.security.principal%,java.naming.security.credentials=%java.naming.security.credentials%]: javax.naming.CommunicationException: Could not obtain connection to any of these urls: vmc-ssrc-rh135:1099 [Root exception is javax.naming.CommunicationException: Failed to connect to server vmc-ssrc-rh135/10.150.30.105:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server vmc-ssrc-rh135/10.150.30.105:1099 [Root exception is java.net.ConnectException: Connection refused]]]
org.hyperic.hq.product.MetricNotFoundException: Can't connect to MBeanServer [java.naming.provider.url=jnp%3A//vmc-ssrc-rh135%3A1099,java.naming.security.principal=%java.naming.security.principal%,java.naming.security.credentials=%java.naming.security.credentials%]: javax.naming.CommunicationException: Could not obtain connection to any of these urls: vmc-ssrc-rh135:1099 [Root exception is javax.naming.CommunicationException: Failed to connect to server vmc-ssrc-rh135/10.150.30.105:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server vmc-ssrc-rh135/10.150.30.105:1099 [Root exception is java.net.ConnectException: Connection refused]]]
at org.hyperic.hq.plugin.jboss.JBoss5MeasurementPlugin.getValue(JBoss5MeasurementPlugin.java:69)
at org.hyperic.hq.product.MeasurementPluginManager.getPluginValue(MeasurementPluginManager.java:176)
at org.hyperic.hq.product.MeasurementPluginManager.getValue(MeasurementPluginManager.java:274)
at org.hyperic.hq.product.MeasurementPluginManager.getValue(MeasurementPluginManager.java:135)
at org.hyperic.hq.product.MeasurementPluginManager.getValue(MeasurementPluginManager.java:127)
at org.hyperic.hq.measurement.agent.server.MeasurementCommandsService.getMeasurements(MeasurementCommandsService.java:201)
at org.hyperic.hq.measurement.agent.server.MeasurementCommandsServer.dispatchCommand(MeasurementCommandsServer.java:169)
at org.hyperic.hq.agent.server.CommandDispatcher.processRequest(CommandDispatcher.java:112)
at org.hyperic.hq.agent.server.CommandListener.listenLoop(CommandListener.java:191)
at org.hyperic.hq.agent.server.AgentDaemon.start(AgentDaemon.java:848)
at org.hyperic.hq.agent.server.AgentDaemon$RunnableAgent.run(AgentDaemon.java:930)
at java.lang.Thread.run(Unknown Source)
Caused by: org.hyperic.hq.product.MetricUnreachableException: Can't connect to MBeanServer [java.naming.provider.url=jnp%3A//vmc-ssrc-rh135%3A1099,java.naming.security.principal=%java.naming.security.principal%,java.naming.security.credentials=%java.naming.security.credentials%]: javax.naming.CommunicationException: Could not obtain connection to any of these urls: vmc-ssrc-rh135:1099 [Root exception is javax.naming.CommunicationException: Failed to connect to server vmc-ssrc-rh135/10.150.30.105:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server vmc-ssrc-rh135/10.150.30.105:1099 [Root exception is java.net.ConnectException: Connection refused]]]
at org.hyperic.hq.plugin.jboss.JBossUtil.unreachable(JBossUtil.java:207)
at org.hyperic.hq.plugin.jboss.JBossUtil.getRemoteMBeanValue(JBossUtil.java:291)
at org.hyperic.hq.plugin.jboss.JBossMeasurementPlugin.getValue(JBossMeasurementPlugin.java:58)
at org.hyperic.hq.plugin.jboss.JBoss5MeasurementPlugin.getValue(JBoss5MeasurementPlugin.java:63)
... 11 more
Caused by: javax.naming.CommunicationException: Could not obtain connection to any of these urls: vmc-ssrc-rh135:1099 [Root exception is javax.naming.CommunicationException: Failed to connect to server vmc-ssrc-rh135/10.150.30.105:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server vmc-ssrc-rh135/10.150.30.105:1099 [Root exception is java.net.ConnectException: Connection refused]]]
at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1725)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:689)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:682)
at javax.naming.InitialContext.lookup(Unknown Source)
at org.hyperic.hq.plugin.jboss.JBossUtil.getMBeanServer(JBossUtil.java:141)
at org.hyperic.hq.plugin.jboss.JBossUtil.getMBeanServer(JBossUtil.java:168)
at org.hyperic.hq.plugin.jboss.JBossUtil.getRemoteMBeanValue(JBossUtil.java:289)
... 13 more
Caused by: javax.naming.CommunicationException: Failed to connect to server vmc-ssrc-rh135/10.150.30.105:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server vmc-ssrc-rh135/10.150.30.105:1099 [Root exception is java.net.ConnectException: Connection refused]]
at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:331)
at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1696)
... 19 more
Caused by: javax.naming.ServiceUnavailableException: Failed to connect to server vmc-ssrc-rh135/10.150.30.105:1099 [Root exception is java.net.ConnectException: Connection refused]
at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:301)
... 20 more
Caused by: java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(Unknown Source)
at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
at java.net.PlainSocketImpl.connect(Unknown Source)
at java.net.SocksSocketImpl.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:97)
at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:82)
at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:297)
... 20 more

Expected Result:
The control action start completes successfully and reports no error

Actual Result:
The control action start does not complete successfully and report an error

Steps to Reproduce:
1. Install and start hq-agent on platform running JBoss 5.0.x
2. Log into Hyperic
3. Select platform running JBoss 5.0.x server
4. Select JBoss sever from Deployed Health Servers
5. Click the Control tab
6. Ensure the JBoss server is stopped
7. Select start from the drop down list in the Quick Control section
8. Click the play button to execute control action restart
9. Note the process does not complete and errors

Additional Information:
See attached agent.log for additonal information.

Activity

Hide
Frederic Calindas added a comment -

Also, control action START does not work with JBoss 6.0; however, failed message is different than reported with JBoss 5.0.

f/bootstrap.xml Common Base: $JBOSS_HOME/common/ Common Library: $JBOSS_HOME/common/lib/ Server Name: default Server Base: $JBOSS_HOME/server/ Server Library: $JBOSS_HOME/server/default/lib/ Server Config: $JBOSS_HOME/server/default/conf/ Server Home: $JBOSS_HOME/server/default/ Server Data: $JBOSS_HOME/server/default/data/ Server Log: $JBOSS_HOME/server/default/log/ Server Temp: $JBOSS_HOME/server/default/tmp/ 16:48:45,835 INFO [AbstractServer] Starting: JBossAS [6.0.0.Final "Neo"]

Show
Frederic Calindas added a comment - Also, control action START does not work with JBoss 6.0; however, failed message is different than reported with JBoss 5.0. f/bootstrap.xml Common Base: $JBOSS_HOME/common/ Common Library: $JBOSS_HOME/common/lib/ Server Name: default Server Base: $JBOSS_HOME/server/ Server Library: $JBOSS_HOME/server/default/lib/ Server Config: $JBOSS_HOME/server/default/conf/ Server Home: $JBOSS_HOME/server/default/ Server Data: $JBOSS_HOME/server/default/data/ Server Log: $JBOSS_HOME/server/default/log/ Server Temp: $JBOSS_HOME/server/default/tmp/ 16:48:45,835 INFO [AbstractServer] Starting: JBossAS [6.0.0.Final "Neo"]
Hide
Yoav Epelman added a comment -

Bulk change to new components

Show
Yoav Epelman added a comment - Bulk change to new components
Hide
Idan Hod added a comment -

As part of our continuous effort to improve product quality, The Hyperic product team has decided to implement a "zero bug policy" methodology.

Following this methodology, only defects that are planned to be handled in the near future will remain open. Any other defect will be deferred, with the option to be reevaluated if the need arises, or if changes to the Hyperic road-map make such defect a candidate for a fix.

We believe this new process will help create clarity and focus in the Hyperic road-map and ultimately benefit our customer base.

This bug has been deferred as part of the new policy.

We appreciate your cooperation and continues contribution to the improvement of Hyperic.

Show
Idan Hod added a comment - As part of our continuous effort to improve product quality, The Hyperic product team has decided to implement a "zero bug policy" methodology. Following this methodology, only defects that are planned to be handled in the near future will remain open. Any other defect will be deferred, with the option to be reevaluated if the need arises, or if changes to the Hyperic road-map make such defect a candidate for a fix. We believe this new process will help create clarity and focus in the Hyperic road-map and ultimately benefit our customer base. This bug has been deferred as part of the new policy. We appreciate your cooperation and continues contribution to the improvement of Hyperic.

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved:
    Last comment:
    41 weeks, 3 days ago