[jira] [Closed] (AMQ-4470) Stomp 1.0 Heartbeat does not work for stomp ssl

["Erik (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/AMQ-4470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Erik closed AMQ-4470.
---------------------


Fixed in ActiveMQ 5.8
                
> Stomp 1.0 Heartbeat does not work for stomp ssl
> -----------------------------------------------
>
>                 Key: AMQ-4470
>                 URL: https://issues.apache.org/jira/browse/AMQ-4470
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: stomp
>    Affects Versions: 5.6.0
>         Environment: Linux: Ubuntu 12.04.1 LTS
> java version "1.7.0_09"
> OpenJDK Runtime Environment (IcedTea7 2.3.3) (7u9-2.3.3-0ubuntu1~12.04.1)
> OpenJDK Client VM (build 23.2-b09, mixed mode, sharing)
>            Reporter: Erik
>              Labels: activemq, beat, heart, heartbeat, ssl, stomp, transport.defaultHeartBeat, transportConnector
>             Fix For: 5.x
>
>
> The Stomp 1.0 Heartbeat feature does not work for stomp+ssl or stomp+nio+ssl URIs. I created a client that sends a request-reply message every 30s with a defaultHeartBeat of 5000 (5s). The Stomp Inactivity Monitor closes the connection for plain stomp URIs. stomp+ssl URIs do not get closed.
> Works:
> <transportConnector name="stomp" uri="stomp://0.0.0.0:61613?transport.defaultHeartBeat=5000,0"/>
> Does not work:
> <transportConnector name="stomp+ssl" uri="stomp+ssl://0.0.0.0:61613?transport.defaultHeartBeat=5000,0"/>
> <transportConnector name="stomp+nio+ssl" uri="stomp+nio+ssl://0.0.0.0:61613?transport.defaultHeartBeat=5000,0"/>

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira