yawl - Case 9.3.1 : Pass - 1798 ms @ 2014-11-25T21:30:22.898Z

Case Description

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

Case Expectation

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

Case Outcome

Received text message of length 4194304.

Expected:
{}

Observed:
[]

Case Closing Behavior

Connection was properly closed (OK)

Opening Handshake

GET /runCase?case=263&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: lmqtzS0r24hIl036IFOEGw==
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: tOJYIsstCN5onbA/HQllLbQB1wk=

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
6	336	2016
10	1	10
12	1	12
14	2	28
18	1	18
22	1	22
26	1	26
28	1	28
40	1	40
44	1	44
48	1	48
52	2	104
56	2	112
58	1	58
60	1	60
62	1	62
64	310	19840
68	1	68
70	1329	93030
72	1	72
74	1	74
76	764	58064
78	1	78
80	1	80
82	2	164
84	2	168
86	2	172
90	1	90
92	1	92
94	3	282
98	2	196
100	3	300
102	3	306
108	4	432
110	1	110
112	3	336
114	2	228
116	2	232
118	1	118
120	1	120
122	1	122
124	2	248
130	1	130
132	1	132
134	1102	147668
136	1	136
140	11529	1614060
146	980	143080
174	1	174
204	638	130152
210	293	61530
216	19	4104
235	1	235
274	28	7672
280	49	13720
286	12	3432
344	3	1032
350	10	3500
356	1	356
420	5	2100
554	1	554
624	1	624
3150	1	3150
3926	1	3926
7904	1	7904
14776	1	14776
22406	1	22406
26222	1	26222
46784	1	46784
54074	1	54074
65514	1	65514
65520	4	262080
65526	27	1769202
Total	17514	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
1	1
8	1
Total	65600

Frames Transmitted by Opcode

Opcode	Count
0	65536
1	1
8	1
Total	65538

Wire Log

000 RX OCTETS: 474554202f72756e436173653f636173653d323633266167656e743d7961776c20485454502f312e310d0a436f6e6e656374

               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: 8880c61a899c

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

007 TCP DROPPED BY ME