[ 
https://issues.apache.org/jira/browse/QPID-7397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chuck Rolke updated QPID-7397:
------------------------------
    Attachment: qpidd-session-channel-65535.html

Trace showing qpidd broker running amqpnetlite self test twice. First instance 
passes and broker returns Begin with remote channel 0; second instance fails 
when broker returns Begin with remote channel null.

> [C++ broker] Broker replies with RemoteChannel null instead of zero
> -------------------------------------------------------------------
>
>                 Key: QPID-7397
>                 URL: https://issues.apache.org/jira/browse/QPID-7397
>             Project: Qpid
>          Issue Type: Bug
>          Components: C++ Broker
>    Affects Versions: qpid-cpp-0.34
>         Environment: qpid-cpp master (as of aug-8) running on fedora 23
> amqpnetlite master (as of aug-19) running on WinServer 2012 R2
> Self test LinkTests_SessionCreateClose
>            Reporter: Chuck Rolke
>         Attachments: qpidd-session-channel-65535.html
>
>
> The self test is pretty simple
> {noformat}
> public void TestMethod_SessionCreateClose()
> {
>     Connection connection = new Connection(testTarget.Address);
>     Session session = new Session(connection);
>     session.Close(0);
>     connection.Close();
>     Assert.IsTrue(connection.Error == null, "connection has error!");
> }
> {noformat}
> Normally the test passes. Over the wire the init, open, begin, end, and close 
> performatives are interleaved. Every now and then the test fails apparently 
> when the client gets to send 'begin, end' or 'begin, end, close' back-to-back 
> before the broker replies with the bad begin frame. 
> A browsable trace of the failed AMQP handshake will be attached shortly. In 
> this trace the first connection from 10.18.96.1:13423 is a success. The 
> second connection (in red) from 18.18.96.1:13425 failed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to