Uploaded image for project: 'JBoss A-MQ'
  1. JBoss A-MQ
  2. ENTMQ-803

'java.net.SocketException: Connection reset' WARN occurs on the broker with a slow consumer and when producer reaches queue memory limit

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Done
    • Affects Version/s: JBoss A-MQ 6.1, JBoss A-MQ 6.2
    • Fix Version/s: JBoss A-MQ 6.2.1
    • Component/s: broker
    • Labels:
    • Environment:

      JBoss Fuse (6.1.0.redhat-379) after applying Rollup Patch JBoss 6.1 Rollup 1, jboss-fuse-6.2.0.redhat-102

      Description

      After applying patch JBoss 6.1 Rollup 1 to JBoss Fuse (6.1.0.redhat-379), and running the tests attached (entmq803-test.zip), the following errors occur in the fuse.log:

      19:36:14,837 | WARN  | xception Handler | Transport                        | 131 - org.apache.activemq.activemq-osgi - 5.9.0.redhat-610394 | Transport Connection to: tcp://127.0.0.1:45768 failed: java.net.SocketException: Connection reset
      19:36:15,890 | WARN  | xception Handler | Transport                        | 131 - org.apache.activemq.activemq-osgi - 5.9.0.redhat-610394 | Transport Connection to: tcp://127.0.0.1:45774 failed: java.net.SocketException: Broken pipe
      

      The test and broker run on the same host.
      At the end all messages were received.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  ganeshmurthy Ganesh Murthy
                  Reporter:
                  emedvede Elena Medvedeva
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  5 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: