You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "R.I.Pienaar (JIRA)" <ji...@apache.org> on 2012/06/22 22:19:42 UTC
[jira] [Created] (AMQ-3897) Stomp 1.1 keep alive does not work with
stomp+nio
R.I.Pienaar created AMQ-3897:
--------------------------------
Summary: Stomp 1.1 keep alive does not work with stomp+nio
Key: AMQ-3897
URL: https://issues.apache.org/jira/browse/AMQ-3897
Project: ActiveMQ
Issue Type: Bug
Components: Broker, stomp
Affects Versions: 5.6.0
Environment: centos 6, OpenJDK 64-Bit Server VM (build 20.0-b12, mixed mode)
Reporter: R.I.Pienaar
using the transport:
<pre>
<transportConnector name="stomp+nio" uri="stomp+nio://0.0.0.0:6163"/>
</pre>
When connecting a stomp 1.1 client I see this using tcpdump:
<pre>
send...>
CONNECT
.passcode:xxx.host:kvm4.content-length:0.heart-beat:30000,30000.content-type:text/plain; charset=UTF-8.login:rip.accept-version:1.1,1.0...
<...receive
CONNECTED.heart-beat:0,0.session:ID:kvm4-55239-1340217683781-3:10008.server:ActiveMQ/5.6.0.version:1.1....
</pre>
Notice that I send the heart-beat header requesting 30000,30000 heartbeats but then ActiveMQ replies with 0,0
If I change the stomp transport to stomp and not stomp+nio and not changing my code or what I send in CONNECT request I get the correct heartbeats.
It seems stomp+nio does not have heartbeat support for protocol 1.1
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (AMQ-3897) Stomp 1.1 keep alive does not work with
stomp+nio
Posted by "R.I.Pienaar (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQ-3897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
R.I.Pienaar updated AMQ-3897:
-----------------------------
Description:
using the transport:
{quote}
<transportConnector name="stomp+nio" uri="stomp+nio://0.0.0.0:6163"/>
{quote}
When connecting a stomp 1.1 client I see this using tcpdump (tcpdump output so new lines etc):
{quote}
send...>
CONNECT
.passcode:xxx.host:kvm4.content-length:0.heart-beat:30000,30000.content-type:text/plain; charset=UTF-8.login:rip.accept-version:1.1,1.0...
<...receive
CONNECTED.heart-beat:0,0.session:ID:kvm4-55239-1340217683781-3:10008.server:ActiveMQ/5.6.0.version:1.1....
{quote}
Notice that I send the heart-beat header requesting 30000,30000 heartbeats but then ActiveMQ replies with 0,0
If I change the stomp transport to stomp and not stomp+nio and not changing my code or what I send in CONNECT request I get the correct heartbeats.
It seems stomp+nio does not have heartbeat support for protocol 1.1
was:
using the transport:
{quote}
<transportConnector name="stomp+nio" uri="stomp+nio://0.0.0.0:6163"/>
{quote}
When connecting a stomp 1.1 client I see this using tcpdump:
{quote}
send...>
CONNECT
.passcode:xxx.host:kvm4.content-length:0.heart-beat:30000,30000.content-type:text/plain; charset=UTF-8.login:rip.accept-version:1.1,1.0...
<...receive
CONNECTED.heart-beat:0,0.session:ID:kvm4-55239-1340217683781-3:10008.server:ActiveMQ/5.6.0.version:1.1....
{quote}
Notice that I send the heart-beat header requesting 30000,30000 heartbeats but then ActiveMQ replies with 0,0
If I change the stomp transport to stomp and not stomp+nio and not changing my code or what I send in CONNECT request I get the correct heartbeats.
It seems stomp+nio does not have heartbeat support for protocol 1.1
> Stomp 1.1 keep alive does not work with stomp+nio
> -------------------------------------------------
>
> Key: AMQ-3897
> URL: https://issues.apache.org/jira/browse/AMQ-3897
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker, stomp
> Affects Versions: 5.6.0
> Environment: centos 6, OpenJDK 64-Bit Server VM (build 20.0-b12, mixed mode)
> Reporter: R.I.Pienaar
>
> using the transport:
> {quote}
> <transportConnector name="stomp+nio" uri="stomp+nio://0.0.0.0:6163"/>
> {quote}
> When connecting a stomp 1.1 client I see this using tcpdump (tcpdump output so new lines etc):
> {quote}
> send...>
> CONNECT
> .passcode:xxx.host:kvm4.content-length:0.heart-beat:30000,30000.content-type:text/plain; charset=UTF-8.login:rip.accept-version:1.1,1.0...
> <...receive
> CONNECTED.heart-beat:0,0.session:ID:kvm4-55239-1340217683781-3:10008.server:ActiveMQ/5.6.0.version:1.1....
> {quote}
> Notice that I send the heart-beat header requesting 30000,30000 heartbeats but then ActiveMQ replies with 0,0
> If I change the stomp transport to stomp and not stomp+nio and not changing my code or what I send in CONNECT request I get the correct heartbeats.
> It seems stomp+nio does not have heartbeat support for protocol 1.1
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (AMQ-3897) Stomp 1.1 keep alive does not work
with stomp+nio
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQ-3897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Bish resolved AMQ-3897.
-------------------------------
Resolution: Fixed
Fix Version/s: 5.7.0
Assignee: Timothy Bish
Fixed in trunk.
> Stomp 1.1 keep alive does not work with stomp+nio
> -------------------------------------------------
>
> Key: AMQ-3897
> URL: https://issues.apache.org/jira/browse/AMQ-3897
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker, stomp
> Affects Versions: 5.6.0
> Environment: centos 6, OpenJDK 64-Bit Server VM (build 20.0-b12, mixed mode)
> Reporter: R.I.Pienaar
> Assignee: Timothy Bish
> Fix For: 5.7.0
>
>
> using the transport:
> {quote}
> <transportConnector name="stomp+nio" uri="stomp+nio://0.0.0.0:6163"/>
> {quote}
> When connecting a stomp 1.1 client I see this using tcpdump (tcpdump output so new lines etc):
> {quote}
> send...>
> CONNECT
> .passcode:xxx.host:kvm4.content-length:0.heart-beat:30000,30000.content-type:text/plain; charset=UTF-8.login:rip.accept-version:1.1,1.0...
> <...receive
> CONNECTED.heart-beat:0,0.session:ID:kvm4-55239-1340217683781-3:10008.server:ActiveMQ/5.6.0.version:1.1....
> {quote}
> Notice that I send the heart-beat header requesting 30000,30000 heartbeats but then ActiveMQ replies with 0,0
> If I change the stomp transport to stomp and not stomp+nio and not changing my code or what I send in CONNECT request I get the correct heartbeats.
> It seems stomp+nio does not have heartbeat support for protocol 1.1
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQ-3897) Stomp 1.1 keep alive does not work
with stomp+nio
Posted by "R.I.Pienaar (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQ-3897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13403890#comment-13403890 ]
R.I.Pienaar commented on AMQ-3897:
----------------------------------
Thanks for sorting this out! I see it's targeted for 5.7.x, could this be 5.6.x instead? its just a bug fix and would be awesome to get this working before 5.7.0
> Stomp 1.1 keep alive does not work with stomp+nio
> -------------------------------------------------
>
> Key: AMQ-3897
> URL: https://issues.apache.org/jira/browse/AMQ-3897
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker, stomp
> Affects Versions: 5.6.0
> Environment: centos 6, OpenJDK 64-Bit Server VM (build 20.0-b12, mixed mode)
> Reporter: R.I.Pienaar
> Assignee: Timothy Bish
> Fix For: 5.7.0
>
>
> using the transport:
> {quote}
> <transportConnector name="stomp+nio" uri="stomp+nio://0.0.0.0:6163"/>
> {quote}
> When connecting a stomp 1.1 client I see this using tcpdump (tcpdump output so new lines etc):
> {quote}
> send...>
> CONNECT
> .passcode:xxx.host:kvm4.content-length:0.heart-beat:30000,30000.content-type:text/plain; charset=UTF-8.login:rip.accept-version:1.1,1.0...
> <...receive
> CONNECTED.heart-beat:0,0.session:ID:kvm4-55239-1340217683781-3:10008.server:ActiveMQ/5.6.0.version:1.1....
> {quote}
> Notice that I send the heart-beat header requesting 30000,30000 heartbeats but then ActiveMQ replies with 0,0
> If I change the stomp transport to stomp and not stomp+nio and not changing my code or what I send in CONNECT request I get the correct heartbeats.
> It seems stomp+nio does not have heartbeat support for protocol 1.1
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (AMQ-3897) Stomp 1.1 keep alive does not work with
stomp+nio
Posted by "R.I.Pienaar (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQ-3897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
R.I.Pienaar updated AMQ-3897:
-----------------------------
Description:
using the transport:
{quote}
<transportConnector name="stomp+nio" uri="stomp+nio://0.0.0.0:6163"/>
{quote}
When connecting a stomp 1.1 client I see this using tcpdump:
{quote}
send...>
CONNECT
.passcode:xxx.host:kvm4.content-length:0.heart-beat:30000,30000.content-type:text/plain; charset=UTF-8.login:rip.accept-version:1.1,1.0...
<...receive
CONNECTED.heart-beat:0,0.session:ID:kvm4-55239-1340217683781-3:10008.server:ActiveMQ/5.6.0.version:1.1....
{quote}
Notice that I send the heart-beat header requesting 30000,30000 heartbeats but then ActiveMQ replies with 0,0
If I change the stomp transport to stomp and not stomp+nio and not changing my code or what I send in CONNECT request I get the correct heartbeats.
It seems stomp+nio does not have heartbeat support for protocol 1.1
was:
using the transport:
<pre>
<transportConnector name="stomp+nio" uri="stomp+nio://0.0.0.0:6163"/>
</pre>
When connecting a stomp 1.1 client I see this using tcpdump:
<pre>
send...>
CONNECT
.passcode:xxx.host:kvm4.content-length:0.heart-beat:30000,30000.content-type:text/plain; charset=UTF-8.login:rip.accept-version:1.1,1.0...
<...receive
CONNECTED.heart-beat:0,0.session:ID:kvm4-55239-1340217683781-3:10008.server:ActiveMQ/5.6.0.version:1.1....
</pre>
Notice that I send the heart-beat header requesting 30000,30000 heartbeats but then ActiveMQ replies with 0,0
If I change the stomp transport to stomp and not stomp+nio and not changing my code or what I send in CONNECT request I get the correct heartbeats.
It seems stomp+nio does not have heartbeat support for protocol 1.1
> Stomp 1.1 keep alive does not work with stomp+nio
> -------------------------------------------------
>
> Key: AMQ-3897
> URL: https://issues.apache.org/jira/browse/AMQ-3897
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker, stomp
> Affects Versions: 5.6.0
> Environment: centos 6, OpenJDK 64-Bit Server VM (build 20.0-b12, mixed mode)
> Reporter: R.I.Pienaar
>
> using the transport:
> {quote}
> <transportConnector name="stomp+nio" uri="stomp+nio://0.0.0.0:6163"/>
> {quote}
> When connecting a stomp 1.1 client I see this using tcpdump:
> {quote}
> send...>
> CONNECT
> .passcode:xxx.host:kvm4.content-length:0.heart-beat:30000,30000.content-type:text/plain; charset=UTF-8.login:rip.accept-version:1.1,1.0...
> <...receive
> CONNECTED.heart-beat:0,0.session:ID:kvm4-55239-1340217683781-3:10008.server:ActiveMQ/5.6.0.version:1.1....
> {quote}
> Notice that I send the heart-beat header requesting 30000,30000 heartbeats but then ActiveMQ replies with 0,0
> If I change the stomp transport to stomp and not stomp+nio and not changing my code or what I send in CONNECT request I get the correct heartbeats.
> It seems stomp+nio does not have heartbeat support for protocol 1.1
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira