yawl - Case 9.8.6 : Pass - 40002 ms @ 2014-11-25T21:36:31.440Z
Case Description
Send 1000 binary messages of payload size 4096 to measure implementation/network RTT (round trip time) / latency.
Case Expectation
Receive echo'ed binary messages (with payload as sent). Timeout case after 480 secs.
Case Outcome
Ok, received all echo'ed messages in time.
Expected:
{}
Observed:
[]
Case Closing Behavior
Connection was properly closed (OK)
GET /runCase?case=304&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: 1HAinZNMjY0f+DXom6lz2w== 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: ObSHhS+OTyLrFjF+Zk/JXLjqLNA=
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). |
Chop Size | Count | Octets |
6 | 1 | 6 |
8 | 1000 | 8000 |
235 | 1 | 235 |
4096 | 1000 | 4096000 |
Total | 2002 | 4104241 |
Chop Size | Count | Octets |
4 | 1 | 4 |
170 | 1 | 170 |
4100 | 1000 | 4100000 |
Total | 1002 | 4100174 |
Opcode | Count |
2 | 1000 |
8 | 1 |
Total | 1001 |
Opcode | Count |
2 | 1000 |
8 | 1 |
Total | 1001 |
000 RX OCTETS: 474554202f72756e436173653f636173653d333034266167656e743d7961776c20485454502f312e310d0a436f6e6e656374
696f6e3a206b6565702d616c6976 ...
001 TX OCTETS: 485454502f312e312031303120537769746368696e672050726f746f636f6c730d0a5365727665723a204175746f6261686e
5465737453756974652f302e372e ...
002 WIRELOG DISABLED
003 CLOSE CONNECTION AFTER 480.000000 sec
004 WIRELOG ENABLED
005 TX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=2, MASK=None, PAYLOAD-REPEAT-LEN=None, CHOPSIZE=None, SYNC=False
0x03e8
006 TX OCTETS: 880203e8
007 RX OCTETS: 8880cbe304c1
008 RX FRAME : OPCODE=8, FIN=True, RSV=0, PAYLOAD-LEN=0, MASKED=True, MASK=6362653330346331
009 TCP DROPPED BY ME