Effective October 27, 2012, online and email support for FuseSource products will move to Red Hat support channels. For more information, please see the JIRA Migration to Red Hat FAQ.
As of October 27th, please open all new issues in the Red Hat Customer Portal .
Issue Details (XML | Word | Printable)

Key: HQ-155
Type: Bug Bug
Status: Closed Closed
Resolution: Won't Fix
Priority: Major Major
Assignee: Jane Murphey
Reporter: Swathy Nimbagiri
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Fuse HQ

Problems with Control actions for a Broker service of Fuse MB

Created: 11/Sep/09 11:31 AM   Updated: 23/Oct/12 02:45 PM
Component/s: None
Affects Version/s: 4.1
Fix Version/s: 4.1

Environment:
WinXP, IE7
Fuse MB - 5.3
Issue Links:
Linked
 


 Description  « Hide
When the control action 'Start' is attempted on a Broker Service from HQ, it fails with the following error message -
-------------------------------------
Method 'start' invocation error [org.apache.activemq:Type=Broker,BrokerName=localhost]: java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: localhost; nested exception is: java.net.ConnectException: Connection refused: connect]

-------------------------------------

When the Broker Service is already started and the 'Start' control action is taken on it, the action shows successful. However, it actually fails to start a stopped Broker service.

Note that, the 'Stop' Control action works fine when the Broker is started by stopping it. However, the following error message occurs when the 'Stop' Control action is taken on an already stopped Broker service.
-----------------------------
Method 'stop' invocation error [org.apache.activemq:Type=Broker,BrokerName=localhost]: java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: localhost; nested exception is: java.net.ConnectException: Connection refused: connect]
-----------------------------

It would be good if we disable the irrelevant control actions based on the broker service state. ex: disable stop,gc,removeTopic,removeQueue control actions when broker is already stopped

Or we can atleast show up an appropriate message to the user indicating the invalid action taken. ex: 'Stop' Control action is invalid since the broker is already stopped.



 All   Comments   Change History      Sort Order: Ascending order - Click to sort in descending order
Saraswathi Krishnan added a comment - 13/Oct/09 12:08 PM
Selecting the "removeTopic/removeQueue" control action for a broker service, and typing the "Topic/Queue" name to be removed and executing it, shows the action as successful. However , when we view the activeMQ web console - the Topic/Queue is not removed.

Also typing the "Topic/Queue" name in the search box displays the Topic/Queue name (which was supposed to have been removed through the control action of the broker service).


Amanda Hall added a comment - 20/Nov/09 05:44 PM
Paul ..is this resolved as a result of your recent work?

Paul Taylor added a comment - 24/Nov/09 11:01 AM
Testing with jconsole and ActiveMQ in ServiceMix, the stop() operation on the broker stops the broker and removes all mbeans so the start operation cannot succeed. Even reinstalling the activemq feature does not bring back the mbeans or the broker. This is most likely the cause of the java.net.ConnectException exceptions.

For the Queues/Topics, removing a queue does not remove the underlying Hyperic service so it will still appear even though the queue has been removed. If the queue is later recreated it will reuse the existing Hyperic service entry.


Amanda Hall added a comment - 25/Nov/09 12:20 PM
Can you document this as a restriction?