[
https://issues.apache.org/jira/browse/TINKERPOP-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16058159#comment-16058159
]
Charlie commented on TINKERPOP-1695:
------------------------------------
Sorry, I wasn't exactly being clear. From what I understand, there's two things
at play: 1) the websocket connection and 2) the "sessionOpProcessor" session.
I was attempting to re-use the websocket connection after a close session call
(op='close' processr='session'), which works. Also, I might have run into
another bug where closing doesn't actually work, so I'd like to see
confirmation that my close worked. What I'd like to see (and almost see,
except one part):
{code}
client --> server: socket open
client <--> server: commands (with session set)
client --> server: op='close' processor='session'
client <-- server: **Confirmation of successful close**
client <--> server: commands (with other session set)
...
client --> server: socket close
client <-- server: socket close
{code}
The "Confirmation of successful close" part is what I'm not seeing. Even with
no "other session" commands sent, and waiting a while before websocket close, I
don't see any confirmation of the close.
Attached to this report is a screen shot of Wireshark showing what's happening.
The second to last packet shown is the close message sent from the client. The
following message is a TCP ack that isn't a websocket frame or with any
payload. Is this the 'NO CONTENT' message? If so, this won't work with any
websocket library that expects a response.
!pcap_ws.png|thumbnail!
> Session close over websocket does not reply with confirmation
> -------------------------------------------------------------
>
> Key: TINKERPOP-1695
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1695
> Project: TinkerPop
> Issue Type: Bug
> Components: server
> Affects Versions: 3.2.3, 3.2.4
> Environment: Ubuntu 14.04
> Reporter: Charlie
> Priority: Minor
> Attachments: pcap_ws.png
>
>
> If you were to open up wireshark and monitor the websocket traffic and run
> the following in the gremlin console, you will see that a close message will
> get sent, but no confirmation back that the session actually closed.
> {code:java}
> gremlin> :remote console tinkerpop.server conf/remote.yaml session
> gremlin> :> g.V().count()
> gremlin> :remote close
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
