[
https://issues.apache.org/activemq/browse/AMQ-1298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brent Rahn closed AMQ-1298.
---------------------------
Resolution: Cannot Reproduce
Found this was a problem with stomp library code.
> Stomp address connections remain active
> ---------------------------------------
>
> Key: AMQ-1298
> URL: https://issues.apache.org/activemq/browse/AMQ-1298
> Project: ActiveMQ
> Issue Type: Bug
> Components: Connector
> Affects Versions: 4.1.1
> Environment: Debian Linux
> Reporter: Brent Rahn
> Priority: Critical
>
> When a stomp client issues a DISCONNECT command the client is disconnected
> and the stomp connection is removed from ActiveMQ. When looking at the
> server using jconsole, you can see another subfolder under Connection->stomp
> called address. The connections never drop out of this address folder,
> eventually this takes up all of the threads on the system and ActiveMQ stops
> accepting connections. The logs show an OutOfMemory exception when this
> occurs.
> If you examine the properties for the connections under
> Connection->stomp->address you can see that addresses associated with valid
> connections have a value in the ConnectionId field. The addresses associated
> with connections that have disconnected display "Unavailable" in the
> ConnectionId field.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
