[PROTON-1286] [proton-c] pipelined incoming open-begin-end triggers bad Begin response

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: proton-0.13.1
• Fix Version/s: proton-c-future
• Component/s: proton-c
• Environment: qpid-proton master (as of aug-23) running on fedora 23. Example 'server_direct -a localhost:5672/q1'; ; amqpnetlite master (as of aug-19) running on WinServer 2012 R2; Self test LinkTests_SessionCreateClose
• Assignee: Unassigned
• Reporter: Charles E. Rolke
• Created: 23/Aug/16 14:56
• Updated: 04/Nov/16 14:36

Description

This issue is a duplicate of https://issues.apache.org/jira/browse/QPID-7397

I suspect that there is a race condition in proton where the incoming stream of events creates a session and then deletes it before the proton client (be it server_direct or qpidd) can reply with the session creation response.

The response would normally be a Begin(channel=0, RemoteChannel=0) but since the session is deleted the response goes out as Begin(channel=0, RemoteChannel=null). This makes it look like a new session is being created.

Issue Links

• relates to: QPID-7397 [C++ broker] Broker replies with RemoteChannel null instead of zero