activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xiaohua Guan (JIRA)" <>
Subject [jira] [Created] (AMQ-4217) Transport Connection to: tcp://XX.XX.XX.XX:52509 failed: Connection reset
Date Tue, 11 Dec 2012 05:35:23 GMT
Xiaohua Guan created AMQ-4217:

             Summary: Transport Connection to: tcp://XX.XX.XX.XX:52509 failed:
Connection reset
                 Key: AMQ-4217
             Project: ActiveMQ
          Issue Type: Bug
          Components: stomp
    Affects Versions: 5.7.0
         Environment: Ubuntu 12.04, Stomp 1.1.10
            Reporter: Xiaohua Guan

I am using mcollective(1.3.1-19) in Ubuntu 12.04, which is connecting to activemq server via
stomp protocol. 

After a topic was subscribed for a long time (> 8 hours), the exception "
Connection reset" occurred in file activemq.log when trying to publish a message on the topic.

Related information is pasted below.

1. Exception stack trace Connection reset
        at org.apache.activemq.transport.tcp.TcpBufferedInputStream.fill(
        at org.apache.activemq.transport.tcp.TcpTransport$2.fill(
        at org.apache.activemq.transport.tcp.TcpTransport$
        at org.apache.activemq.transport.stomp.StompWireFormat.readHeaderLine(
        at org.apache.activemq.transport.stomp.StompWireFormat.readLine(
        at org.apache.activemq.transport.stomp.StompWireFormat.parseAction(
        at org.apache.activemq.transport.stomp.StompWireFormat.unmarshal(
        at org.apache.activemq.transport.tcp.TcpTransport.readCommand(
        at org.apache.activemq.transport.tcp.TcpTransport.doRun(

2. conf/active.xml(only the related parts)

            <transportConnector name="openwire" uri="tcp://"/>
            <transportConnector name="stomp" uri="stomp://"/>

3. stomp connection parameters = XXX.XXX.XXX.XXX
plugin.stomp.port = 6163
plugin.stomp.user = mcollective
plugin.stomp.password = XXXXXXX

Could you tell me how to solve the problem or bug?

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message