You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Michael Justin (JIRA)" <ji...@apache.org> on 2008/07/25 15:05:00 UTC

[jira] Commented: (AMQ-1737) Broker does not reply to command messages

    [ https://issues.apache.org/activemq/browse/AMQ-1737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=44538#action_44538 ] 

Michael Justin commented on AMQ-1737:
-------------------------------------

Problem also exisits using the web admin interface:

* start admin console
* navigate to Topic "ActiveMQ.Agent"
* send a message with content 'list' and 'Reply To'='MyReplyQueue'
* check ActiveMQ log file

so it seems not to be a STOMP related problem.

Can somebody confirm? Maybe it is just a simple configuration problem.

> Broker does not reply to command messages
> -----------------------------------------
>
>                 Key: AMQ-1737
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1737
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.1.0
>            Reporter: Michael Justin
>
> In ActiveMQ 5.1.0 and 5.2-snapshot (Windows distribution) I have uncommented the commandAgent configuration so that it reads
> <commandAgent xmlns="http://activemq.apache.org/schema/core" brokerUrl="vm://localhost"/>
> However, I cannot send commands to ActiveMQ using the STOMP protocol, regardless of the servername I use in the connection (localhost, 127.0.0.1 or the local IP address). I have included the exception message below. It looks like something with RMI goes wrong. I use Windows 2000 SP 4.
> In ActiveMQ 5.0, the commandAgent works fine. 
> Best Regards
> Michael Justin
> ERROR CommandMessageListener         - Failed to process message due to: java.la
> ng.Exception: java.io.IOException: Failed to retrieve RMIServer stub: javax.nami
> ng.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Con
> nection refused to host: localhost; nested exception is:
>         java.net.ConnectException: Connection refused: connect]. Message: Active
> MQTextMessage {commandId = 4, responseRequired = false, messageId = ID:michael-1
> 090-1211215893984-5:0:-1:1:1, originalDestination = null, originalTransactionId
> = null, producerId = ID:michael-1090-1211215893984-5:0:-1:1, destination = topic
> ://ActiveMQ.Agent, transactionId = null, expiration = 0, timestamp = 12112160160
> 78, arrival = 0, brokerInTime = 1211216016078, brokerOutTime = 1211216016078, co
> rrelationId = null, replyTo = queue://HabariExpressAdmin, persistent = false, ty
> pe = null, priority = 0, groupID = null, groupSequence = 0, targetConsumerId = n
> ull, compressed = false, userID = null, content = null, marshalledProperties = n
> ull, dataStructure = null, redeliveryCounter = 0, size = 1024, properties = null
> , readOnlyProperties = true, readOnlyBody = true, droppable = false, text = quer
> y -QQueue=* --view Name}
> java.lang.Exception: java.io.IOException: Failed to retrieve RMIServer stub: jav
> ax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectExcepti
> on: Connection refused to host: localhost; nested exception is:
>         java.net.ConnectException: Connection refused: connect]
>         at org.apache.activemq.console.command.QueryCommand.runTask(QueryCommand
> .java:118)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.