Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-5047

Many opened JMS sessions cause connection timed out

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Icon: Major Major
    • 10.0.0.CR3
    • 10.0.0.Alpha6
    • JMS
    • None
    • Hide

      1. create JMS queue
      2. deploy 30 MDB with maxSession property set on 60
      3. sent 10 000 000 messages

      Show
      1. create JMS queue 2. deploy 30 MDB with maxSession property set on 60 3. sent 10 000 000 messages

      When 30 MDB consumers are deployed with property maxSession set on 60, the server stops to accept connections and the connection timed out exception is thrown. However when 60 MDB consumers are deployed with property maxSession set on 30, the server accepts connection as expected, only "Failed to open a socket" exception is occurred, because maximum of opened sockets is reached.

            jmesnil1@redhat.com Jeff Mesnil
            eduda_jira Erich Duda (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: