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

[Jeff Mesnil (JIRA)]

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

Jeff Mesnil resolved WFLY-5047.
-------------------------------
    Fix Version/s: 10.0.0.CR3
       Resolution: Cannot Reproduce


Issue no longer occurs with WFLY 10.0.0.CR3

> 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
>             Fix For: 10.0.0.CR3
>
>         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.4.11#64026)