You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Daniel Lujan (JIRA)" <ji...@apache.org> on 2009/10/13 19:59:55 UTC
[jira] Issue Comment Edited: (AMQNET-196) ActiveMQ 5.3 /
System.IO.EndOfStreamException / "Unable to read beyond the end of the
stream.
[ https://issues.apache.org/activemq/browse/AMQNET-196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=54734#action_54734 ]
Daniel Lujan edited comment on AMQNET-196 at 10/13/09 10:58 AM:
----------------------------------------------------------------
I do some test while inspect with 'WireShark' protocol analyzer, and I see:
1) AMQ-5.2 send a Keep-Alive command each 20 seconds, client answer with Keep-Alive Command.
324 14:37:59.665777 192.168.2.99 192.168.2.24 TCP 61616 > fjippol-swrly [PSH, ACK] Seq=406 Ack=585 Win=64951 Len=10
325 14:37:59.665898 192.168.2.24 192.168.2.99 TCP fjippol-swrly > 61616 [PSH, ACK] Seq=585 Ack=416 Win=65120 Len=10
326 14:37:59.835978 192.168.2.99 192.168.2.24 TCP 61616 > fjippol-swrly [ACK] Seq=416 Ack=595 Win=64941 Len=0
2) AMQ-5.3 send a Keep-Alive command each 20 seconds, client NOT answer with (only ACK-TCP).
261 14:33:44.620817 192.168.2.99 192.168.2.24 TCP 61616 > tsb2 [PSH, ACK] Seq=356 Ack=535 Win=65001 Len=10
262 14:33:44.807736 192.168.2.24 192.168.2.99 TCP tsb2 > 61616 [ACK] Seq=535 Ack=366 Win=65170 Len=0
Alway data is:
00 00 00 06 0a 00 00 00 00 00
(Keep-Alive command)
192.168.2.99 AMQ
192.168.2.24 CLIENT
was (Author: lujan99):
I do some test while inspect with 'WireShark' protocol analyzer, and I see:
1) AMQ-5.2 send a Keep-Alive command each 20 seconds, client answer with Keep-Alive Command.
324 14:37:59.665777 192.168.2.99 192.168.2.24 TCP 61616 > fjippol-swrly [PSH, ACK] Seq=406 Ack=585 Win=64951 Len=10
325 14:37:59.665898 192.168.2.24 192.168.2.99 TCP fjippol-swrly > 61616 [PSH, ACK] Seq=585 Ack=416 Win=65120 Len=10
326 14:37:59.835978 192.168.2.99 192.168.2.24 TCP 61616 > fjippol-swrly [ACK] Seq=416 Ack=595 Win=64941 Len=0
2) AMQ-5.2 send a Keep-Alive command each 20 seconds, client NOT answer with (only ACK-TCP).
261 14:33:44.620817 192.168.2.99 192.168.2.24 TCP 61616 > tsb2 [PSH, ACK] Seq=356 Ack=535 Win=65001 Len=10
262 14:33:44.807736 192.168.2.24 192.168.2.99 TCP tsb2 > 61616 [ACK] Seq=535 Ack=366 Win=65170 Len=0
Alway data is:
00 00 00 06 0a 00 00 00 00 00
(Keep-Alive command)
192.168.2.99 AMQ
192.168.2.24 CLIENT
> ActiveMQ 5.3 / System.IO.EndOfStreamException / "Unable to read beyond the end of the stream.
> ---------------------------------------------------------------------------------------------
>
> Key: AMQNET-196
> URL: https://issues.apache.org/activemq/browse/AMQNET-196
> Project: ActiveMQ .Net
> Issue Type: Bug
> Affects Versions: 1.1.0
> Environment: Windows-server-2003
> AMQ 5.3 RC4
> Apache.NMS.ActiveMQ, Version 1.1.0.1642
> Reporter: Daniel Lujan
> Assignee: Timothy Bish
> Fix For: 1.2.0
>
> Attachments: nmsTest.cs
>
>
> using "Assembly Apache.NMS.ActiveMQ, Version 1.1.0.1642"
> when I use:
> connection = CreateConnection();
> connection.ExceptionListener += new ExceptionListener(OnException);
> session = connection.CreateSession(this.SessionAcknowledgeMode);
> ....
>
> each 60 seconds I get a exception :
> "Unable to read beyond the end of the stream."
> its not necessary a message.... is automatic.
> I upload my test in:
> http://www.nabble.com/file/p25862392/nmsTest.cs
> ticket:
> http://www.nabble.com/NMS---ActiveMQ-5.3----%22Unable-to-read-beyond-the-end-of-the-stream.%22-td25849938.html
> exception type is >>> System.IO.EndOfStreamException
> note: with ActiveMQ 5.2 I don't have this issue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.