[jboss-jira] [JBoss JIRA] (WFLY-5047) Many opened JMS sessions cause connection timed out

[Erich Duda (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-5047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Erich Duda moved JBEAP-568 to WFLY-5047:
----------------------------------------

              Project: WildFly  (was: JBoss Enterprise Application Platform)
                  Key: WFLY-5047  (was: JBEAP-568)
             Workflow: GIT Pull Request workflow   (was: CDW v1)
    Affects Version/s: 10.0.0.Alpha6
                           (was: EAP 7.0.0.DR6)
          Component/s: JMS
                           (was: JMS)
       Target Release:   (was: EAP 7.0.0.GA)


> Many opened JMS sessions cause connection timed out
> ---------------------------------------------------
>
>                 Key: WFLY-5047
>                 URL: https://issues.jboss.org/browse/WFLY-5047
>             Project: WildFly
>          Issue Type: Bug
>          Components: JMS
>    Affects Versions: 10.0.0.Alpha6
>         Environment: Fedora 22
> Open JDK 8
>            Reporter: Erich Duda
>            Assignee: Jeff Mesnil
>         Attachments: 30MDB60maxSession.log
>
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)