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

RabbitMQ 2.1 no longer supported with Hyperic 4.6.0

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Critical Critical
  • Resolution: Fixed
  • Affects Version/s: 4.6
  • Fix Version/s: 4.6, 4.x Sprint 28
  • Component/s: Plugins
  • Environment:
    Hyperic server 4.6.0-EE-230 on CentOS 5.4 x64 with external MySQL DB
    Hyperic agent 4.6.0-EE-230 on RHEL 5.4 x64
     - RabbitMQ 2.1 running on agent platform
  • Case Links:
    none
  • Regression:
    No
  • Tags:

Description

RabbitMQ 2.1 no longer supported with Hyperic 4.6.0

After auto-discovery of RabbitMQ, configuration results in an error:

The configuration has not been set for this resource due to : Invalid configuration: Plugin error: [/api/nodes/rabbit%40vmc-ssrc-rh82] http error code: '404'

This questions what versions should be supported. Previously 2.0 and 2.1 were supported including multinode. Now versions 2.2.0, 2.3.0, 2.3.1, 2.4.0, 2.4.1, 2.5.0 and 2.5.1 are available.

Expected Result:
Updated plugins maintain functionality for last supported application versions

Actual Result:
Newer RabbitMQ plugin does not support older plugin API (not sure what version API changed)

Steps to Reproduce:

  1. Install and start RabbitMQ 2.1
  2. Install Hyperic agent on RabbitMQ platform
  3. Log into Hyperic
  4. Note auto-discovery of RabbitMQ platform
  5. Add RabbitMQ platform to inventory from AIQ
  6. Select RabbitMQ Server
  7. Note Configuration error
  8. Attempt to configure server
  9. Note Configuration error as before
  1. agent-2k335.log
    21/Jul/11 3:01 PM
    673 kB
    Frederic Calindas
  2. agent-rh82.log
    21/Jul/11 3:01 PM
    450 kB
    Frederic Calindas

Activity

Hide
German Laullon added a comment -

Added support for old RabbitMQ old API (2.1)

Show
German Laullon added a comment - Added support for old RabbitMQ old API (2.1)
Hide
Frederic Calindas added a comment -

Installation of latest 4.6.0 agent build (247) on RabbitMQ Server 2.1.1 on Windows 2003 OR RabbitMQ Server 2.1.0 on RHEL 5.4 x64 does allow RabbitMQ Server to be properly auto-discovered.

RabbitMQ Server 2.1.1 on Windows 2003 is running multi-node.
RabbitMQ Server 2.1.0 on RHEL 5.5 is running single node.

Both logs report:

2011-07-21 15:57:04,138 ERROR [Thread-3] [AutoScan] AutoScan failed for RabbitMQ
java.lang.IllegalStateException: Invalid use of SingleClientConnManager: connection still allocated.
Make sure to release the connection before allocating another one.
	at org.apache.http.impl.conn.SingleClientConnManager.getConnection(SingleClientConnManager.java:216)
	at org.apache.http.impl.conn.SingleClientConnManager$1.getConnection(SingleClientConnManager.java:190)
	at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:391)
	at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:820)
	at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:754)
	at org.hyperic.hq.plugin.rabbitmq.core.HypericRabbitAdmin.get(HypericRabbitAdmin.java:237)
	at org.hyperic.hq.plugin.rabbitmq.core.HypericRabbitAdmin.getChannels(HypericRabbitAdmin.java:166)
	at org.hyperic.hq.plugin.rabbitmq.detect.RabbitServerDetector.generateSignature(RabbitServerDetector.java:358)
	at org.hyperic.hq.plugin.rabbitmq.detect.RabbitServerDetector.getServerResources(RabbitServerDetector.java:98)
	at org.hyperic.hq.autoinventory.scanimpl.NullScan.scan(NullScan.java:83)
	at org.hyperic.hq.autoinventory.Scanner.start(Scanner.java:198)
	at org.hyperic.hq.autoinventory.ScanManager.mainRunLoop(ScanManager.java:141)
	at org.hyperic.hq.autoinventory.ScanManager.access$000(ScanManager.java:41)
	at org.hyperic.hq.autoinventory.ScanManager$1.run(ScanManager.java:107)

See attached agent-2k335.log and agent-rh82.log for complete log information.

Show
Frederic Calindas added a comment - Installation of latest 4.6.0 agent build (247) on RabbitMQ Server 2.1.1 on Windows 2003 OR RabbitMQ Server 2.1.0 on RHEL 5.4 x64 does allow RabbitMQ Server to be properly auto-discovered. RabbitMQ Server 2.1.1 on Windows 2003 is running multi-node. RabbitMQ Server 2.1.0 on RHEL 5.5 is running single node. Both logs report:
2011-07-21 15:57:04,138 ERROR [Thread-3] [AutoScan] AutoScan failed for RabbitMQ
java.lang.IllegalStateException: Invalid use of SingleClientConnManager: connection still allocated.
Make sure to release the connection before allocating another one.
	at org.apache.http.impl.conn.SingleClientConnManager.getConnection(SingleClientConnManager.java:216)
	at org.apache.http.impl.conn.SingleClientConnManager$1.getConnection(SingleClientConnManager.java:190)
	at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:391)
	at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:820)
	at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:754)
	at org.hyperic.hq.plugin.rabbitmq.core.HypericRabbitAdmin.get(HypericRabbitAdmin.java:237)
	at org.hyperic.hq.plugin.rabbitmq.core.HypericRabbitAdmin.getChannels(HypericRabbitAdmin.java:166)
	at org.hyperic.hq.plugin.rabbitmq.detect.RabbitServerDetector.generateSignature(RabbitServerDetector.java:358)
	at org.hyperic.hq.plugin.rabbitmq.detect.RabbitServerDetector.getServerResources(RabbitServerDetector.java:98)
	at org.hyperic.hq.autoinventory.scanimpl.NullScan.scan(NullScan.java:83)
	at org.hyperic.hq.autoinventory.Scanner.start(Scanner.java:198)
	at org.hyperic.hq.autoinventory.ScanManager.mainRunLoop(ScanManager.java:141)
	at org.hyperic.hq.autoinventory.ScanManager.access$000(ScanManager.java:41)
	at org.hyperic.hq.autoinventory.ScanManager$1.run(ScanManager.java:107)
See attached agent-2k335.log and agent-rh82.log for complete log information.
Hide
German Laullon added a comment -

HTTP Response must be read in order to "close" the connection.

Show
German Laullon added a comment - HTTP Response must be read in order to "close" the connection.
Hide
Frederic Calindas added a comment -

Verified with Hyperic Server Daily Build 4.6.0-EE-252 (7/28/11) and upgraded agent va UI.

RabbitMQ 2.1.0 on RHEL and RabbitMQ 2.1.1 on Windows working.

Show
Frederic Calindas added a comment - Verified with Hyperic Server Daily Build 4.6.0-EE-252 (7/28/11) and upgraded agent va UI. RabbitMQ 2.1.0 on RHEL and RabbitMQ 2.1.1 on Windows working.

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved:
    Last comment:
    2 years, 38 weeks, 3 days ago