[
https://issues.apache.org/jira/browse/AMQ-2361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish closed AMQ-2361.
-----------------------------
Resolution: Incomplete
Not test to help reproduce the issue. Likely since the user is disabling the
inactivity monitor their app is closing connections abruptly and they are then
lingering on the broker side.
> No Of connections Increases at Server end
> ------------------------------------------
>
> Key: AMQ-2361
> URL: https://issues.apache.org/jira/browse/AMQ-2361
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.2.0
> Environment: Linux
> Reporter: rk
> Fix For: 5.6.0
>
>
> We are running ActiveMQ 5.2 and we had set the maxInactivityTimeOUt=0 in the
> server URL
> There are many clients which connects to this Activemq. The issue here is
> with the number of connections,
> Lets say a client has 20 connections to activemq it will be always constantly
> remain at 20 if we check the number of connections to activemq from CLIENT end
> If we check the number of connections fromSERVER (activemq) it will show more
> than 20 connections from the same client and the same keeps increasing by 1
> or 2 after every few hours.
> This creates lot of issues as the total connections increases beyond limit
> (i.e., in thousands)
> Earlier we were using 4.1.1 with the same configuration. I saw this issue is
> resolved in 5.2, hence we are using the same but issue is occurring in 5.2
> also.
> Please let me know if there is any fix for the same.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
