yawl - Case 9.4.1 : Pass - 1868 ms @ 2014-11-25T21:30:25.716Z

Case Description

Send fragmented binary message message with message payload of length 4 * 2**20 (4M). Sent out in fragments of 64.

Case Expectation

Receive echo'ed binary message (with payload as sent).

Case Outcome

Received binary message of length 4194304.

Expected:
{}

Observed:
[]

Case Closing Behavior

Connection was properly closed (OK)

Opening Handshake

GET /runCase?case=272&agent=yawl HTTP/1.1
Connection: keep-alive, Upgrade
Pragma: no-cache
Cache-Control: no-cache
Upgrade: websocket
Sec-WebSocket-Version: 13
Sec-WebSocket-Key: Y+ZZVYEMbb1XTtotTN3grA==
Host: localhost:9001

HTTP/1.1 101 Switching Protocols
Server: AutobahnTestSuite/0.7.1-0.9.3-3
Upgrade: WebSocket
Connection: Upgrade
Sec-WebSocket-Accept: 3LaB/JGsHc1DqwJjgTQ+4vx/Gds=

Closing Behavior

Key	Value	Description
isServer	True	True, iff I (the fuzzer) am a server, and the peer is a client.
closedByMe	True	True, iff I have initiated closing handshake (that is, did send close first).
failedByMe	False	True, iff I have failed the WS connection (i.e. due to protocol error). Failing can be either by initiating closing handshake or brutal drop TCP.
droppedByMe	True	True, iff I dropped the TCP connection.
wasClean	True	True, iff full WebSockets closing handshake was performed (close frame sent and received) _and_ the server dropped the TCP (which is its responsibility).
wasNotCleanReason	None	When wasClean == False, the reason what happened.
wasServerConnectionDropTimeout	False	When we are a client, and we expected the server to drop the TCP, but that didn't happen in time, this gets True.
wasOpenHandshakeTimeout	False	When performing the opening handshake, but the peer did not finish in time, this gets True.
wasCloseHandshakeTimeout	False	When we initiated a closing handshake, but the peer did not respond in time, this gets True.
localCloseCode	1000	The close code I sent in close frame (if any).
localCloseReason	None	The close reason I sent in close frame (if any).
remoteCloseCode	None	The close code the peer sent me in close frame (if any).
remoteCloseReason	None	The close reason the peer sent me in close frame (if any).

Wire Statistics

Octets Received by Chop Size

Chop Size	Count	Octets
2	1	2
6	904	5424
8	1	8
12	1	12
16	1	16
20	1	20
22	1	22
24	1	24
28	3	84
30	1	30
36	1	36
38	1	38
40	1	40
44	1	44
46	1	46
52	1	52
54	1	54
56	1	56
60	1	60
62	1	62
64	809	51776
70	2905	203350
72	1	72
74	1	74
76	2731	207556
78	1	78
80	2	160
82	1	82
86	2	172
90	3	270
94	3	282
96	1	96
102	3	306
106	1	106
108	3	324
110	1	110
112	2	224
116	1	116
118	2	236
120	2	240
122	2	244
128	2	256
130	2	260
132	2	264
134	2778	372252
136	1	136
140	9991	1398740
146	142	20732
174	1	174
190	1	190
204	143	29172
210	142	29820
216	7	1512
235	1	235
274	11	3014
280	24	6720
286	2	572
344	1	344
350	3	1050
420	1	420
490	1	490
910	1	910
1750	1	1750
3430	1	3430
3926	1	3926
6720	1	6720
12986	1	12986
22406	1	22406
46784	1	46784
54074	1	54074
65514	1	65514
65520	4	262080
65526	27	1769202
Total	20699	4588139

Octets Transmitted by Chop Size

Chop Size	Count	Octets
2	1	2
4	1	4
66	65536	4325376
170	1	170
Total	65539	4325552

Frames Received by Opcode

Opcode	Count
0	65598
2	1
8	1
Total	65600

Frames Transmitted by Opcode

Opcode	Count
0	65536
2	1
8	1
Total	65538

Wire Log

000 RX OCTETS: 474554202f72756e436173653f636173653d323732266167656e743d7961776c20485454502f312e310d0a436f6e6e656374

               696f6e3a206b6565702d616c6976 ...

001 TX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e

               5465737453756974652f302e372e ...

002 CLOSE CONNECTION AFTER 100.000000 sec

003 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False

               0x03e8

004 TX OCTETS: 880203e8

005 RX OCTETS: 8880e1c09d08

006 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=0, MASKED=True, MASK=6531633039643038

007 TCP DROPPED BY ME