activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <>
Subject [jira] [Closed] (AMQ-6797) wss connections not being closed on ActiveMQ side
Date Mon, 18 Sep 2017 16:39:00 GMT


Timothy Bish closed AMQ-6797.
    Resolution: Incomplete

No reproducer provided, not enough information to investigate 

> wss connections not being closed on ActiveMQ side
> -------------------------------------------------
>                 Key: AMQ-6797
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Transport
>    Affects Versions: 5.14.0
>         Environment: Debian (SMP Debian 3.16.7-ckt25-2+deb8u3 (2016-07-02) x86_64 GNU/Linux)
on AWS, 4 cores, 7.5GB.
>            Reporter: Marcos Moreno Martin
> We have clients that connect via wss to our ActiveMQ. 
> Under some circumstances, we have socket connections that appear in the ActiveMQ web
console, but when doing a netstat -an we can see that they are not open in the system.
> This means that ActiveMQ is enqueuing messages for that connections, but they are not
> This is the transport configuration:
> {code}
> <transportConnector name="wss" uri="wss://;wireFormat.maxFrameSize=104857600&amp;needClientAuth=true&amp;transport.enabledProtocols=TLSv1,TLSv1.1,TLSv1.2"
allowLinkStealing="true" enableStatusMonitor="true" />
> {code}
> Is there a way of closing these connections? Is this an error solved in a newer release
(could not find it in the release notes)? We have the enableStatusMonitor="true" option, but
still the connection is not being closed on the ActiveMQ side. What we need to do right now
is restarting ActiveMQ, but it is not desired.

This message was sent by Atlassian JIRA

View raw message