[jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1400) Allow users to configure a system wide maximum connection limit

[Tim Fox (JIRA)]

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

Tim Fox updated JBMESSAGING-1400:
---------------------------------

    Fix Version/s: 2.0.0.beta5-tmp
                       (was: 2.0.0.beta5)


> Allow users to configure a system wide maximum connection limit
> ---------------------------------------------------------------
>
>                 Key: JBMESSAGING-1400
>                 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1400
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>            Reporter: Jay Howell
>            Assignee: Tim Fox
>             Fix For: 2.0.0
>
>
> Many users are complaining of errors that say "Too many open files", which comes from the number of sockets open during jms processing. It's currently possible to run the system out of resources.  We currently only have control of this through the remoting/netty/mina layer.  We should have a setting in JBM that limits the number of connections systemwide, that is independent of the remoting protocol/package.  This way users wouldn't have to keep learning a new package/configuration setting each time the communications package changes in jbm.  

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira