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

    • Bug
    • Resolution: Done
    • Minor
    • JBoss A-MQ 6.2.1
    • JBoss A-MQ 6.1, JBoss A-MQ 6.2
    • broker

    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.

      Attachments

        1. entmq803-test.zip
          16 kB
        2. fuse.log
          67 kB

        Issue Links

          is related to

          Bug - A problem that impairs or prevents the functions of the product. ENTMQ-683 Transport java.io.EOFException occurring in broker

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              gmurthy@redhat.com Ganesh Murthy
              emedvede Elena Medvedeva (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: