Mark Soderquist created QPID-6281:
-------------------------------------
Summary: Child of type SessionAdapter already exists with name of 0
Key: QPID-6281
URL: https://issues.apache.org/jira/browse/QPID-6281
Project: Qpid
Issue Type: Bug
Components: Java Broker
Affects Versions: 0.30
Reporter: Mark Soderquist
We are using Mule ESB 3.5.0 with the Qpid 0.30 AMQP 1.0 JMS libraries to
connect to a Qpid 0.30 server and getting the following error:
org.apache.qpid.server.model.AbstractConfiguredObject$DuplicateNameException:
Child of type SessionAdapter already exists with name of 0
Following this error it appears the Qpid server immediately terminates the
socket:
java.net.SocketException: Connection reset
at java.net.SocketInputStream.read(SocketInputStream.java:196)
at java.net.SocketInputStream.read(SocketInputStream.java:122)
at sun.security.ssl.InputRecord.readFully(InputRecord.java:442)
at sun.security.ssl.InputRecord.read(InputRecord.java:480)
at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:927)
at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:884)
at sun.security.ssl.AppInputStream.read(AppInputStream.java:102)
at java.io.InputStream.read(InputStream.java:101)
at
org.apache.qpid.amqp_1_0.client.TCPTransportProvier.doRead(TCPTransportProvier.java:207)
at
org.apache.qpid.amqp_1_0.client.TCPTransportProvier.access$000(TCPTransportProvier.java:43)
at
org.apache.qpid.amqp_1_0.client.TCPTransportProvier$1.run(TCPTransportProvier.java:158)
at java.lang.Thread.run(Thread.java:745)
We don't understand if this is correct behavior that can be remedied or if it
is a bug.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
