You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Christian Pfeiffer <ch...@kaasa.com> on 2010/03/31 15:01:55 UTC
*** SPAM *** Tomcat NIO : CometProcessor
Hello,
I just tried to use the tomcat nio and wondered if it is possible to use
client and server pushes through the same socket connection? Or if I
have to establish to connections for that purpose. In the end the client
should be able to receive notification from server (server push) and
also be able to request certain things. As I understood the "Low Latency
HTTP" document it should be possible. Has anyone any advice for me,
currently the connection gets closed after the second request from
client with error CLIENT_DISCONNECTED.
Thanks in advance
Chris.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat NIO : CometProcessor
Posted by Michael Wojcik <mw...@newsguy.com>.
Filip Hanik - Dev Lists wrote:
>
> you're wrong, I believe it is
>
> chunk-header:blabla<CRLF>
> chunk-data<CRLF>
>
> The spec says
>
> chunk = chunk-size [ chunk-extension ] CRLF
> chunk-data CRLF
>
>
> Hence, the request that was posted here, should have been 16bytes
> header, not 18
Whoops - you are correct. Somehow I overlooked that second "CRLF" when
I checked 3.1.6. I should have checked an implementation and not just
the spec...
(The CRLF after chunk-data exists mostly to make any optional trailers
easier to read, presumably.)
So yes, the chunk-size in the posted request was wrong.
--
Michael Wojcik
Micro Focus
Rhetoric & Writing, Michigan State University
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat NIO : CometProcessor
Posted by Filip Hanik - Dev Lists <de...@hanik.com>.
you're wrong, I believe it is
chunk-header:blabla<CRLF>
chunk-data<CRLF>
The spec says
chunk = chunk-size [ chunk-extension ] CRLF
chunk-data CRLF
Hence, the request that was posted here, should have been 16bytes
header, not 18
Filip
On 04/01/2010 11:23 AM, Michael Wojcik wrote:
> Filip Hanik - Dev Lists wrote:
>
>> I just skimmed this through, but from what I remember, the CRLF after
>> </xml> should not be counted into your "chunk header"
>>
> No, the chunk-size is the entire length of the chunk. Since a chunked
> content-body can include any sort of data, it wouldn't make sense to
> exclude trailing whitespace characters - the content might not be of a
> type where "whitespace characters" were defined.
>
> See RFC 2616 3.6.1:
>
> chunk-data = chunk-size(OCTET)
>
> There must be exactly as many octets as specified in chunk-size.
>
> What I don't see in the trace are the zero-size chunks that terminate
> the chunked content-bodies.
>
> In frame 12, the client closes the connection (sends a FIN); that
> would appear to be why Tomcat is reporting the client closed the
> connection.
>
> Of course this is only a half-close, and the server *could* still send
> a response, but RFC 2616 doesn't acknowledge the half-close mechanism
> in TCP. From 4.4:
>
> 5.By the server closing the connection. (Closing the connection
> cannot be used to indicate the end of a request body, since that
> would leave no possibility for the server to send back a response.)
>
> This is, depending on your viewpoint, an error, oversight, or
> restriction in HTTP; but in effect it means that if the client closes
> its end of the conversation after sending a request but before
> receiving a response, the the server is free to consider the
> connection closed (even though it isn't) and discard the request.
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat NIO : CometProcessor
Posted by Michael Wojcik <mw...@newsguy.com>.
Filip Hanik - Dev Lists wrote:
>
> I just skimmed this through, but from what I remember, the CRLF after
> </xml> should not be counted into your "chunk header"
No, the chunk-size is the entire length of the chunk. Since a chunked
content-body can include any sort of data, it wouldn't make sense to
exclude trailing whitespace characters - the content might not be of a
type where "whitespace characters" were defined.
See RFC 2616 3.6.1:
chunk-data = chunk-size(OCTET)
There must be exactly as many octets as specified in chunk-size.
What I don't see in the trace are the zero-size chunks that terminate
the chunked content-bodies.
In frame 12, the client closes the connection (sends a FIN); that
would appear to be why Tomcat is reporting the client closed the
connection.
Of course this is only a half-close, and the server *could* still send
a response, but RFC 2616 doesn't acknowledge the half-close mechanism
in TCP. From 4.4:
5.By the server closing the connection. (Closing the connection
cannot be used to indicate the end of a request body, since that
would leave no possibility for the server to send back a response.)
This is, depending on your viewpoint, an error, oversight, or
restriction in HTTP; but in effect it means that if the client closes
its end of the conversation after sending a request but before
receiving a response, the the server is free to consider the
connection closed (even though it isn't) and discard the request.
--
Michael Wojcik
Micro Focus
Rhetoric & Writing, Michigan State University
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat NIO : CometProcessor
Posted by Filip Hanik - Dev Lists <de...@hanik.com>.
On 03/31/2010 09:29 AM, Christian Pfeiffer wrote:
> 31 32
Let's take a look at the data you are sending
0040 36 17 31 32 0d 0a 3c 78 6d 6c 3e 48 65 6c 6c 6f 6.12..<xml>Hello
0050 3c 2f 78 6d 6c 3e 0d 0a </xml>..
Your Chunk header: 31 32
That represents : 12
Which means, Tomcat will expect 18 bytes after the 0d 0a
The data you send:
0040 3c 78 6d 6c 3e 48 65 6c 6c 6f <xml>Hello
0050 3c 2f 78 6d 6c 3e </xml>
I count 16 bytes.
I just skimmed this through, but from what I remember, the CRLF after
</xml> should not be counted into your "chunk header"
Filip
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat NIO : CometProcessor
Posted by Christian Pfeiffer <ch...@kaasa.com>.
Here the raw data:
No. Time Source Destination Protocol
Info
1 0.000000 127.0.0.1 127.0.0.1 TCP
46356 > http-alt [SYN] Seq=0 Win=32792 Len=0 MSS=16396 TSV=5912087
TSER=0 WS=6
Frame 1 (74 bytes on wire, 74 bytes captured)
Ethernet II, Src: 00:00:00_00:00:00 (00:00:00:00:00:00), Dst:
00:00:00_00:00:00 (00:00:00:00:00:00)
Internet Protocol, Src: 127.0.0.1 (127.0.0.1), Dst: 127.0.0.1 (127.0.0.1)
Transmission Control Protocol, Src Port: 46356 (46356), Dst Port:
http-alt (8080), Seq: 0, Len: 0
0000 00 00 00 00 00 00 00 00 00 00 00 00 08 00 45 00 ..............E.
0010 00 3c b1 bc 40 00 40 06 8a fd 7f 00 00 01 7f 00 .<..@.@.........
0020 00 01 b5 14 1f 90 33 e8 87 ab 00 00 00 00 a0 02 ......3.........
0030 80 18 c8 e4 00 00 02 04 40 0c 04 02 08 0a 00 5a ........@......Z
0040 36 17 00 00 00 00 01 03 03 06 6.........
No. Time Source Destination
Protocol Info
2 0.000019 127.0.0.1 127.0.0.1 TCP
http-alt > 46356 [SYN, ACK] Seq=0 Ack=1 Win=32768 Len=0 MSS=16396
TSV=5912087 TSER=5912087 WS=6
Frame 2 (74 bytes on wire, 74 bytes captured)
Ethernet II, Src: 00:00:00_00:00:00 (00:00:00:00:00:00), Dst:
00:00:00_00:00:00 (00:00:00:00:00:00)
Internet Protocol, Src: 127.0.0.1 (127.0.0.1), Dst: 127.0.0.1 (127.0.0.1)
Transmission Control Protocol, Src Port: http-alt (8080), Dst Port:
46356 (46356), Seq: 0, Ack: 1, Len: 0
0000 00 00 00 00 00 00 00 00 00 00 00 00 08 00 45 00 ..............E.
0010 00 3c 00 00 40 00 40 06 3c ba 7f 00 00 01 7f 00 .<..@.@.<.......
0020 00 01 1f 90 b5 14 34 0e e9 03 33 e8 87 ac a0 12 ......4...3.....
0030 80 00 75 68 00 00 02 04 40 0c 04 02 08 0a 00 5a ..uh....@......Z
0040 36 17 00 5a 36 17 01 03 03 06 6..Z6.....
No. Time Source Destination
Protocol Info
3 0.000035 127.0.0.1 127.0.0.1 TCP
46356 > http-alt [ACK] Seq=1 Ack=1 Win=32832 Len=0 TSV=5912087 TSER=5912087
Frame 3 (66 bytes on wire, 66 bytes captured)
Ethernet II, Src: 00:00:00_00:00:00 (00:00:00:00:00:00), Dst:
00:00:00_00:00:00 (00:00:00:00:00:00)
Internet Protocol, Src: 127.0.0.1 (127.0.0.1), Dst: 127.0.0.1 (127.0.0.1)
Transmission Control Protocol, Src Port: 46356 (46356), Dst Port:
http-alt (8080), Seq: 1, Ack: 1, Len: 0
0000 00 00 00 00 00 00 00 00 00 00 00 00 08 00 45 00 ..............E.
0010 00 34 b1 bd 40 00 40 06 8b 04 7f 00 00 01 7f 00 .4..@.@.........
0020 00 01 b5 14 1f 90 33 e8 87 ac 34 0e e9 04 80 10 ......3...4.....
0030 02 01 5c 8b 00 00 01 01 08 0a 00 5a 36 17 00 5a ..\........Z6..Z
0040 36 17 6.
No. Time Source Destination
Protocol Info
4 0.000676 127.0.0.1 127.0.0.1 TCP
[TCP segment of a reassembled PDU]
Frame 4 (193 bytes on wire, 193 bytes captured)
Ethernet II, Src: 00:00:00_00:00:00 (00:00:00:00:00:00), Dst:
00:00:00_00:00:00 (00:00:00:00:00:00)
Internet Protocol, Src: 127.0.0.1 (127.0.0.1), Dst: 127.0.0.1 (127.0.0.1)
Transmission Control Protocol, Src Port: 46356 (46356), Dst Port:
http-alt (8080), Seq: 1, Ack: 1, Len: 127
0000 00 00 00 00 00 00 00 00 00 00 00 00 08 00 45 00 ..............E.
0010 00 b3 b1 be 40 00 40 06 8a 84 7f 00 00 01 7f 00 ....@.@.........
0020 00 01 b5 14 1f 90 33 e8 87 ac 34 0e e9 04 80 18 ......3...4.....
0030 02 01 fe a7 00 00 01 01 08 0a 00 5a 36 17 00 5a ...........Z6..Z
0040 36 17 50 4f 53 54 20 2f 73 74 72 65 61 6d 63 61 6.POST /streamca
0050 6d 5f 67 77 74 2f 73 74 72 65 61 6d 63 61 6d 5f m_gwt/streamcam_
0060 67 77 74 2f 58 4d 4c 41 63 65 43 61 72 64 20 48 gwt/XMLAceCard H
0070 54 54 50 2f 31 2e 31 0d 0a 48 6f 73 74 3a 20 6c TTP/1.1..Host: l
0080 6f 63 61 6c 68 6f 73 74 0d 0a 55 73 65 72 2d 41 ocalhost..User-A
0090 67 65 6e 74 3a 20 4d 6f 7a 69 6c 6c 61 2f 34 2e gent: Mozilla/4.
00a0 30 0d 0a 54 72 61 6e 73 66 65 72 2d 45 6e 63 6f 0..Transfer-Enco
00b0 64 69 6e 67 3a 20 63 68 75 6e 6b 65 64 0d 0a 0d ding: chunked...
00c0 0a .
No. Time Source Destination
Protocol Info
5 0.000685 127.0.0.1 127.0.0.1 TCP
http-alt > 46356 [ACK] Seq=1 Ack=128 Win=32768 Len=0 TSV=5912087
TSER=5912087
Frame 5 (66 bytes on wire, 66 bytes captured)
Ethernet II, Src: 00:00:00_00:00:00 (00:00:00:00:00:00), Dst:
00:00:00_00:00:00 (00:00:00:00:00:00)
Internet Protocol, Src: 127.0.0.1 (127.0.0.1), Dst: 127.0.0.1 (127.0.0.1)
Transmission Control Protocol, Src Port: http-alt (8080), Dst Port:
46356 (46356), Seq: 1, Ack: 128, Len: 0
0000 00 00 00 00 00 00 00 00 00 00 00 00 08 00 45 00 ..............E.
0010 00 34 df 13 40 00 40 06 5d ae 7f 00 00 01 7f 00 .4..@.@.].......
0020 00 01 1f 90 b5 14 34 0e e9 04 33 e8 88 2b 80 10 ......4...3..+..
0030 02 00 5c 0d 00 00 01 01 08 0a 00 5a 36 17 00 5a ..\........Z6..Z
0040 36 17 6.
No. Time Source Destination
Protocol Info
6 0.000794 127.0.0.1 127.0.0.1 TCP
[TCP segment of a reassembled PDU]
Frame 6 (88 bytes on wire, 88 bytes captured)
Ethernet II, Src: 00:00:00_00:00:00 (00:00:00:00:00:00), Dst:
00:00:00_00:00:00 (00:00:00:00:00:00)
Internet Protocol, Src: 127.0.0.1 (127.0.0.1), Dst: 127.0.0.1 (127.0.0.1)
Transmission Control Protocol, Src Port: 46356 (46356), Dst Port:
http-alt (8080), Seq: 128, Ack: 1, Len: 22
0000 00 00 00 00 00 00 00 00 00 00 00 00 08 00 45 00 ..............E.
0010 00 4a b1 bf 40 00 40 06 8a ec 7f 00 00 01 7f 00 .J..@.@.........
0020 00 01 b5 14 1f 90 33 e8 88 2b 34 0e e9 04 80 18 ......3..+4.....
0030 02 01 fe 3e 00 00 01 01 08 0a 00 5a 36 17 00 5a ...>.......Z6..Z
0040 36 17 31 32 0d 0a 3c 78 6d 6c 3e 48 65 6c 6c 6f 6.12..<xml>Hello
0050 3c 2f 78 6d 6c 3e 0d 0a </xml>..
No. Time Source Destination
Protocol Info
7 0.000801 127.0.0.1 127.0.0.1 TCP
http-alt > 46356 [ACK] Seq=1 Ack=150 Win=32768 Len=0 TSV=5912087
TSER=5912087
Frame 7 (66 bytes on wire, 66 bytes captured)
Ethernet II, Src: 00:00:00_00:00:00 (00:00:00:00:00:00), Dst:
00:00:00_00:00:00 (00:00:00:00:00:00)
Internet Protocol, Src: 127.0.0.1 (127.0.0.1), Dst: 127.0.0.1 (127.0.0.1)
Transmission Control Protocol, Src Port: http-alt (8080), Dst Port:
46356 (46356), Seq: 1, Ack: 150, Len: 0
0000 00 00 00 00 00 00 00 00 00 00 00 00 08 00 45 00 ..............E.
0010 00 34 df 14 40 00 40 06 5d ad 7f 00 00 01 7f 00 .4..@.@.].......
0020 00 01 1f 90 b5 14 34 0e e9 04 33 e8 88 41 80 10 ......4...3..A..
0030 02 00 5b f7 00 00 01 01 08 0a 00 5a 36 17 00 5a ..[........Z6..Z
0040 36 17 6.
No. Time Source Destination
Protocol Info
8 0.012085 127.0.0.1 127.0.0.1 TCP
[TCP segment of a reassembled PDU]
Frame 8 (311 bytes on wire, 311 bytes captured)
Ethernet II, Src: 00:00:00_00:00:00 (00:00:00:00:00:00), Dst:
00:00:00_00:00:00 (00:00:00:00:00:00)
Internet Protocol, Src: 127.0.0.1 (127.0.0.1), Dst: 127.0.0.1 (127.0.0.1)
Transmission Control Protocol, Src Port: http-alt (8080), Dst Port:
46356 (46356), Seq: 1, Ack: 150, Len: 245
0000 00 00 00 00 00 00 00 00 00 00 00 00 08 00 45 00 ..............E.
0010 01 29 df 15 40 00 40 06 5c b7 7f 00 00 01 7f 00 .)..@.@.\.......
0020 00 01 1f 90 b5 14 34 0e e9 04 33 e8 88 41 80 18 ......4...3..A..
0030 02 00 ff 1d 00 00 01 01 08 0a 00 5a 36 1a 00 5a ...........Z6..Z
0040 36 17 48 54 54 50 2f 31 2e 31 20 32 30 30 20 4f 6.HTTP/1.1 200 O
0050 4b 0d 0a 53 65 72 76 65 72 3a 20 41 70 61 63 68 K..Server: Apach
0060 65 2d 43 6f 79 6f 74 65 2f 31 2e 31 0d 0a 53 65 e-Coyote/1.1..Se
0070 74 2d 43 6f 6f 6b 69 65 3a 20 4a 53 45 53 53 49 t-Cookie: JSESSI
0080 4f 4e 49 44 3d 41 46 32 45 38 43 32 30 37 38 38 ONID=AF2E8C20788
0090 32 34 34 46 36 33 38 35 41 43 38 42 41 35 45 37 244F6385AC8BA5E7
00a0 41 46 30 37 33 3b 20 50 61 74 68 3d 2f 73 74 72 AF073; Path=/str
00b0 65 61 6d 63 61 6d 5f 67 77 74 0d 0a 54 72 61 6e eamcam_gwt..Tran
00c0 73 66 65 72 2d 45 6e 63 6f 64 69 6e 67 3a 20 63 sfer-Encoding: c
00d0 68 75 6e 6b 65 64 0d 0a 44 61 74 65 3a 20 57 65 hunked..Date: We
00e0 64 2c 20 33 31 20 4d 61 72 20 32 30 31 30 20 31 d, 31 Mar 2010 1
00f0 35 3a 31 32 3a 30 36 20 47 4d 54 0d 0a 0d 0a 33 5:12:06 GMT....3
0100 32 0d 0a 3c 78 6d 6c 3e 61 6e 73 77 65 72 20 41 2..<xml>answer A
0110 46 32 45 38 43 32 30 37 38 38 32 34 34 46 36 33 F2E8C20788244F63
0120 38 35 41 43 38 42 41 35 45 37 41 46 30 37 33 3c 85AC8BA5E7AF073<
0130 2f 78 6d 6c 3e 0d 0a /xml>..
No. Time Source Destination
Protocol Info
9 0.012100 127.0.0.1 127.0.0.1 TCP
46356 > http-alt [ACK] Seq=150 Ack=246 Win=33920 Len=0 TSV=5912090
TSER=5912090
Frame 9 (66 bytes on wire, 66 bytes captured)
Ethernet II, Src: 00:00:00_00:00:00 (00:00:00:00:00:00), Dst:
00:00:00_00:00:00 (00:00:00:00:00:00)
Internet Protocol, Src: 127.0.0.1 (127.0.0.1), Dst: 127.0.0.1 (127.0.0.1)
Transmission Control Protocol, Src Port: 46356 (46356), Dst Port:
http-alt (8080), Seq: 150, Ack: 246, Len: 0
0000 00 00 00 00 00 00 00 00 00 00 00 00 08 00 45 00 ..............E.
0010 00 34 b1 c0 40 00 40 06 8b 01 7f 00 00 01 7f 00 .4..@.@.........
0020 00 01 b5 14 1f 90 33 e8 88 41 34 0e e9 f9 80 10 ......3..A4.....
0030 02 12 5a ea 00 00 01 01 08 0a 00 5a 36 1a 00 5a ..Z........Z6..Z
0040 36 1a 6.
No. Time Source Destination
Protocol Info
10 3.001530 127.0.0.1 127.0.0.1 HTTP
POST /streamcam_gwt/streamcam_gwt/XMLAceCard HTTP/1.1
Frame 10 (94 bytes on wire, 94 bytes captured)
Ethernet II, Src: 00:00:00_00:00:00 (00:00:00:00:00:00), Dst:
00:00:00_00:00:00 (00:00:00:00:00:00)
Internet Protocol, Src: 127.0.0.1 (127.0.0.1), Dst: 127.0.0.1 (127.0.0.1)
Transmission Control Protocol, Src Port: 46356 (46356), Dst Port:
http-alt (8080), Seq: 150, Ack: 246, Len: 28
[Reassembled TCP Segments (177 bytes): #4(127), #6(22), #10(28)]
Hypertext Transfer Protocol
Frame (94 bytes):
0000 00 00 00 00 00 00 00 00 00 00 00 00 08 00 45 00 ..............E.
0010 00 50 b1 c1 40 00 40 06 8a e4 7f 00 00 01 7f 00 .P..@.@.........
0020 00 01 b5 14 1f 90 33 e8 88 41 34 0e e9 f9 80 18 ......3..A4.....
0030 02 12 fe 44 00 00 01 01 08 0a 00 5a 39 05 00 5a ...D.......Z9..Z
0040 36 1a 31 38 0d 0a 3c 78 6d 6c 3e 48 65 6c 6c 6f 6.18..<xml>Hello
0050 20 61 67 61 69 6e 3c 2f 78 6d 6c 3e 0d 0a again</xml>..
Reassembled TCP (177 bytes):
0000 50 4f 53 54 20 2f 73 74 72 65 61 6d 63 61 6d 5f POST /streamcam_
0010 67 77 74 2f 73 74 72 65 61 6d 63 61 6d 5f 67 77 gwt/streamcam_gw
0020 74 2f 58 4d 4c 41 63 65 43 61 72 64 20 48 54 54 t/XMLAceCard HTT
0030 50 2f 31 2e 31 0d 0a 48 6f 73 74 3a 20 6c 6f 63 P/1.1..Host: loc
0040 61 6c 68 6f 73 74 0d 0a 55 73 65 72 2d 41 67 65 alhost..User-Age
0050 6e 74 3a 20 4d 6f 7a 69 6c 6c 61 2f 34 2e 30 0d nt: Mozilla/4.0.
0060 0a 54 72 61 6e 73 66 65 72 2d 45 6e 63 6f 64 69 .Transfer-Encodi
0070 6e 67 3a 20 63 68 75 6e 6b 65 64 0d 0a 0d 0a 31 ng: chunked....1
0080 32 0d 0a 3c 78 6d 6c 3e 48 65 6c 6c 6f 3c 2f 78 2..<xml>Hello</x
0090 6d 6c 3e 0d 0a 31 38 0d 0a 3c 78 6d 6c 3e 48 65 ml>..18..<xml>He
00a0 6c 6c 6f 20 61 67 61 69 6e 3c 2f 78 6d 6c 3e 0d llo again</xml>.
00b0 0a .
De-chunked entity body (18 bytes):
0000 3c 78 6d 6c 3e 48 65 6c 6c 6f 3c 2f 78 6d 6c 3e <xml>Hello</xml>
0010 0d 0a ..
No. Time Source Destination
Protocol Info
11 3.034313 127.0.0.1 127.0.0.1 TCP
http-alt > 46356 [FIN, ACK] Seq=246 Ack=178 Win=32768 Len=0 TSV=5912845
TSER=5912837
Frame 11 (66 bytes on wire, 66 bytes captured)
Ethernet II, Src: 00:00:00_00:00:00 (00:00:00:00:00:00), Dst:
00:00:00_00:00:00 (00:00:00:00:00:00)
Internet Protocol, Src: 127.0.0.1 (127.0.0.1), Dst: 127.0.0.1 (127.0.0.1)
Transmission Control Protocol, Src Port: http-alt (8080), Dst Port:
46356 (46356), Seq: 246, Ack: 178, Len: 0
0000 00 00 00 00 00 00 00 00 00 00 00 00 08 00 45 00 ..............E.
0010 00 34 df 16 40 00 40 06 5d ab 7f 00 00 01 7f 00 .4..@.@.].......
0020 00 01 1f 90 b5 14 34 0e e9 f9 33 e8 88 5d 80 11 ......4...3..]..
0030 02 00 55 01 00 00 01 01 08 0a 00 5a 39 0d 00 5a ..U........Z9..Z
0040 39 05 9.
No. Time Source Destination
Protocol Info
12 3.071655 127.0.0.1 127.0.0.1 TCP
46356 > http-alt [ACK] Seq=178 Ack=247 Win=33920 Len=0 TSV=5912855
TSER=5912845
Frame 12 (66 bytes on wire, 66 bytes captured)
Ethernet II, Src: 00:00:00_00:00:00 (00:00:00:00:00:00), Dst:
00:00:00_00:00:00 (00:00:00:00:00:00)
Internet Protocol, Src: 127.0.0.1 (127.0.0.1), Dst: 127.0.0.1 (127.0.0.1)
Transmission Control Protocol, Src Port: 46356 (46356), Dst Port:
http-alt (8080), Seq: 178, Ack: 247, Len: 0
0000 00 00 00 00 00 00 00 00 00 00 00 00 08 00 45 00 ..............E.
0010 00 34 b1 c2 40 00 40 06 8a ff 7f 00 00 01 7f 00 .4..@.@.........
0020 00 01 b5 14 1f 90 33 e8 88 5d 34 0e e9 fa 80 10 ......3..]4.....
0030 02 12 54 dd 00 00 01 01 08 0a 00 5a 39 17 00 5a ..T........Z9..Z
0040 39 0d 9.
No. Time Source Destination
Protocol Info
13 8.052879 127.0.0.1 127.0.0.1 TCP
46356 > http-alt [FIN, ACK] Seq=178 Ack=247 Win=33920 Len=0 TSV=5914100
TSER=5912845
Frame 13 (66 bytes on wire, 66 bytes captured)
Ethernet II, Src: 00:00:00_00:00:00 (00:00:00:00:00:00), Dst:
00:00:00_00:00:00 (00:00:00:00:00:00)
Internet Protocol, Src: 127.0.0.1 (127.0.0.1), Dst: 127.0.0.1 (127.0.0.1)
Transmission Control Protocol, Src Port: 46356 (46356), Dst Port:
http-alt (8080), Seq: 178, Ack: 247, Len: 0
0000 00 00 00 00 00 00 00 00 00 00 00 00 08 00 45 00 ..............E.
0010 00 34 b1 c3 40 00 40 06 8a fe 7f 00 00 01 7f 00 .4..@.@.........
0020 00 01 b5 14 1f 90 33 e8 88 5d 34 0e e9 fa 80 11 ......3..]4.....
0030 02 12 4f ff 00 00 01 01 08 0a 00 5a 3d f4 00 5a ..O........Z=..Z
0040 39 0d 9.
No. Time Source Destination
Protocol Info
14 8.052893 127.0.0.1 127.0.0.1 TCP
http-alt > 46356 [ACK] Seq=247 Ack=179 Win=32768 Len=0 TSV=5914100
TSER=5914100
Frame 14 (66 bytes on wire, 66 bytes captured)
Ethernet II, Src: 00:00:00_00:00:00 (00:00:00:00:00:00), Dst:
00:00:00_00:00:00 (00:00:00:00:00:00)
Internet Protocol, Src: 127.0.0.1 (127.0.0.1), Dst: 127.0.0.1 (127.0.0.1)
Transmission Control Protocol, Src Port: http-alt (8080), Dst Port:
46356 (46356), Seq: 247, Ack: 179, Len: 0
0000 00 00 00 00 00 00 00 00 00 00 00 00 08 00 45 00 ..............E.
0010 00 34 00 00 40 00 40 06 3c c2 7f 00 00 01 7f 00 .4..@.@.<.......
0020 00 01 1f 90 b5 14 34 0e e9 fa 33 e8 88 5e 80 10 ......4...3..^..
0030 02 00 4b 2a 00 00 01 01 08 0a 00 5a 3d f4 00 5a ..K*.......Z=..Z
0040 3d f4 =.
Thanks for patience
Chris.
Filip Hanik - Dev Lists schrieb:
> I would need the raw data, not copy paste, I can't make anything out
> of that. Or if you have, a simple test case.
>
> Filip
>
> On 03/31/2010 07:57 AM, Christian Pfeiffer wrote:
>> Hey Filip, thanks for your swift response. Wireshark tells me:
>>
>> //::::Client:::://
>> POST /url/servlet HTTP/1.1
>> Host: localhost:8080
>> User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.0.13)
>> Gecko/2009080315 Ubuntu/9.04 (jaunty) Firefox/3.0.13
>> Transfer-Encoding: chunked
>>
>> 145
>> <some xml></some xml>
>>
>> //::::Server:::://
>> HTTP/1.1 200 OK
>> Server: Apache-Coyote/1.1
>> Set-Cookie: JSESSIONID=F9A0B9BAB695EDB6C51253A24D8989D9;
>> Path=/streamcam_gwt
>> Transfer-Encoding: chunked
>> Date: Mon, 29 Mar 2010 15:44:25 GMT
>>
>> 9a
>> <some answer></some answer>
>>
>> //::::Client:::://
>> 8E
>> <second xml></second xml>
>>
>>
>> beside the hex values which are not set properly, cause I changed the
>> xml for the sake of simplicity it should be fine right? Or do I miss
>> something? BTW the last message(second xml) isnt examined by my
>> servlet, there I already receive event Client_Disconnected instead of
>> a read I expected. Let me know if you need more information.
>>
>> Thanks in advance
>> Chris.
>>
>>
>> Filip Hanik - Dev Lists schrieb:
>>> hi Chris, if the connection is closed, most likely there is some
>>> sort of data error somewhere.
>>> Record your transaction with Wireshark, and we can examine it.
>>>
>>> Low latency http, meaning sending traffic back and forth should be
>>> possible within the body of the request
>>>
>>> Filip
>>>
>>> On 03/31/2010 07:01 AM, Christian Pfeiffer wrote:
>>>> Hello,
>>>>
>>>> I just tried to use the tomcat nio and wondered if it is possible
>>>> to use client and server pushes through the same socket connection?
>>>> Or if I have to establish to connections for that purpose. In the
>>>> end the client should be able to receive notification from server
>>>> (server push) and also be able to request certain things. As I
>>>> understood the "Low Latency HTTP" document it should be possible.
>>>> Has anyone any advice for me, currently the connection gets closed
>>>> after the second request from client with error CLIENT_DISCONNECTED.
>>>>
>>>> Thanks in advance
>>>> Chris.
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>>>> For additional commands, e-mail: users-help@tomcat.apache.org
>>>>
>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>>> For additional commands, e-mail: users-help@tomcat.apache.org
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> For additional commands, e-mail: users-help@tomcat.apache.org
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat NIO : CometProcessor
Posted by Filip Hanik - Dev Lists <de...@hanik.com>.
I would need the raw data, not copy paste, I can't make anything out of
that. Or if you have, a simple test case.
Filip
On 03/31/2010 07:57 AM, Christian Pfeiffer wrote:
> Hey Filip, thanks for your swift response. Wireshark tells me:
>
> //::::Client:::://
> POST /url/servlet HTTP/1.1
> Host: localhost:8080
> User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.0.13)
> Gecko/2009080315 Ubuntu/9.04 (jaunty) Firefox/3.0.13
> Transfer-Encoding: chunked
>
> 145
> <some xml></some xml>
>
> //::::Server:::://
> HTTP/1.1 200 OK
> Server: Apache-Coyote/1.1
> Set-Cookie: JSESSIONID=F9A0B9BAB695EDB6C51253A24D8989D9;
> Path=/streamcam_gwt
> Transfer-Encoding: chunked
> Date: Mon, 29 Mar 2010 15:44:25 GMT
>
> 9a
> <some answer></some answer>
>
> //::::Client:::://
> 8E
> <second xml></second xml>
>
>
> beside the hex values which are not set properly, cause I changed the
> xml for the sake of simplicity it should be fine right? Or do I miss
> something? BTW the last message(second xml) isnt examined by my
> servlet, there I already receive event Client_Disconnected instead of
> a read I expected. Let me know if you need more information.
>
> Thanks in advance
> Chris.
>
>
> Filip Hanik - Dev Lists schrieb:
>> hi Chris, if the connection is closed, most likely there is some sort
>> of data error somewhere.
>> Record your transaction with Wireshark, and we can examine it.
>>
>> Low latency http, meaning sending traffic back and forth should be
>> possible within the body of the request
>>
>> Filip
>>
>> On 03/31/2010 07:01 AM, Christian Pfeiffer wrote:
>>> Hello,
>>>
>>> I just tried to use the tomcat nio and wondered if it is possible to
>>> use client and server pushes through the same socket connection? Or
>>> if I have to establish to connections for that purpose. In the end
>>> the client should be able to receive notification from server
>>> (server push) and also be able to request certain things. As I
>>> understood the "Low Latency HTTP" document it should be possible.
>>> Has anyone any advice for me, currently the connection gets closed
>>> after the second request from client with error CLIENT_DISCONNECTED.
>>>
>>> Thanks in advance
>>> Chris.
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>>> For additional commands, e-mail: users-help@tomcat.apache.org
>>>
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> For additional commands, e-mail: users-help@tomcat.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat NIO : CometProcessor
Posted by Christian Pfeiffer <ch...@kaasa.com>.
Hey Filip, thanks for your swift response. Wireshark tells me:
//::::Client:::://
POST /url/servlet HTTP/1.1
Host: localhost:8080
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.0.13)
Gecko/2009080315 Ubuntu/9.04 (jaunty) Firefox/3.0.13
Transfer-Encoding: chunked
145
<some xml></some xml>
//::::Server:::://
HTTP/1.1 200 OK
Server: Apache-Coyote/1.1
Set-Cookie: JSESSIONID=F9A0B9BAB695EDB6C51253A24D8989D9;
Path=/streamcam_gwt
Transfer-Encoding: chunked
Date: Mon, 29 Mar 2010 15:44:25 GMT
9a
<some answer></some answer>
//::::Client:::://
8E
<second xml></second xml>
beside the hex values which are not set properly, cause I changed the
xml for the sake of simplicity it should be fine right? Or do I miss
something? BTW the last message(second xml) isnt examined by my servlet,
there I already receive event Client_Disconnected instead of a read I
expected. Let me know if you need more information.
Thanks in advance
Chris.
Filip Hanik - Dev Lists schrieb:
> hi Chris, if the connection is closed, most likely there is some sort
> of data error somewhere.
> Record your transaction with Wireshark, and we can examine it.
>
> Low latency http, meaning sending traffic back and forth should be
> possible within the body of the request
>
> Filip
>
> On 03/31/2010 07:01 AM, Christian Pfeiffer wrote:
>> Hello,
>>
>> I just tried to use the tomcat nio and wondered if it is possible to
>> use client and server pushes through the same socket connection? Or
>> if I have to establish to connections for that purpose. In the end
>> the client should be able to receive notification from server (server
>> push) and also be able to request certain things. As I understood the
>> "Low Latency HTTP" document it should be possible. Has anyone any
>> advice for me, currently the connection gets closed after the second
>> request from client with error CLIENT_DISCONNECTED.
>>
>> Thanks in advance
>> Chris.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> For additional commands, e-mail: users-help@tomcat.apache.org
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat NIO : CometProcessor
Posted by Filip Hanik - Dev Lists <de...@hanik.com>.
hi Chris, if the connection is closed, most likely there is some sort of
data error somewhere.
Record your transaction with Wireshark, and we can examine it.
Low latency http, meaning sending traffic back and forth should be
possible within the body of the request
Filip
On 03/31/2010 07:01 AM, Christian Pfeiffer wrote:
> Hello,
>
> I just tried to use the tomcat nio and wondered if it is possible to
> use client and server pushes through the same socket connection? Or if
> I have to establish to connections for that purpose. In the end the
> client should be able to receive notification from server (server
> push) and also be able to request certain things. As I understood the
> "Low Latency HTTP" document it should be possible. Has anyone any
> advice for me, currently the connection gets closed after the second
> request from client with error CLIENT_DISCONNECTED.
>
> Thanks in advance
> Chris.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org