[
https://issues.apache.org/jira/browse/QPID-5722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Samson updated QPID-5722:
---------------------------------
Description:
1. While sending messages to Active broker, the ActiveMQ server was restarted
on the EC2 instance.
2. Running a netstat on the EC2 instance showed that all AMQP sockets were
gone.
3. Running a netstat on the AMQP JMS Client machine showed that 2 AMQP sockets
were still CONNECTED.
4. I took several thread dumps in succession (waiting several minutes in
between) and noticed that the AMQP socket read was hung. Below is 1 of the
relevant Threads:
"Thread-862713" daemon prio=10 tid=0x00007f067c8cb000 nid=0x4664 runnable
[0x00007f05ef332000]
java.lang.Thread.State: RUNNABLE
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:152)
at java.net.SocketInputStream.read(SocketInputStream.java:122)
at java.net.SocketInputStream.read(SocketInputStream.java:108)
at
org.apache.qpid.amqp_1_0.client.Connection.doRead(Connection.java:388)
at
org.apache.qpid.amqp_1_0.client.Connection.access$000(Connection.java:47)
at org.apache.qpid.amqp_1_0.client.Connection$2.run(Connection.java:259)
at java.lang.Thread.run(Thread.java:744)
was:
1. While sending messages to Active broker, the ActiveMQ server was restarted
on the EC2 instance.
2. Running a netstat on the EC2 instance showed that all AMQP sockets were
gone.
3. Running a netstat on the AMQP JMS Client machine showed that 2 AMQP sockets
were still CONNECTED.
4. I took several thread dumps in succession (waiting several minutes in
between) and noticed that the AMQP socket read was hung. Below is the relevant
Thread:
"Thread-862713" daemon prio=10 tid=0x00007f067c8cb000 nid=0x4664 runnable
[0x00007f05ef332000]
java.lang.Thread.State: RUNNABLE
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:152)
at java.net.SocketInputStream.read(SocketInputStream.java:122)
at java.net.SocketInputStream.read(SocketInputStream.java:108)
at
org.apache.qpid.amqp_1_0.client.Connection.doRead(Connection.java:388)
at
org.apache.qpid.amqp_1_0.client.Connection.access$000(Connection.java:47)
at org.apache.qpid.amqp_1_0.client.Connection$2.run(Connection.java:259)
at java.lang.Thread.run(Thread.java:744)
> Client connection read can hang forever since socket timeout is 0
> ------------------------------------------------------------------
>
> Key: QPID-5722
> URL: https://issues.apache.org/jira/browse/QPID-5722
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
> Affects Versions: 0.27
> Environment: Qpid JMS libraries 0.27 SVN revision 1547654
> AMQP JMS Client was running on 64-bit Linux with JDK 1.7
> AMQP Broker was ActiveMQ running on EC2 64-bit Linux
> Reporter: Michael Samson
> Attachments: QPID-5722.patch
>
>
> 1. While sending messages to Active broker, the ActiveMQ server was
> restarted on the EC2 instance.
> 2. Running a netstat on the EC2 instance showed that all AMQP sockets were
> gone.
> 3. Running a netstat on the AMQP JMS Client machine showed that 2 AMQP
> sockets were still CONNECTED.
> 4. I took several thread dumps in succession (waiting several minutes in
> between) and noticed that the AMQP socket read was hung. Below is 1 of the
> relevant Threads:
> "Thread-862713" daemon prio=10 tid=0x00007f067c8cb000 nid=0x4664 runnable
> [0x00007f05ef332000]
> java.lang.Thread.State: RUNNABLE
> at java.net.SocketInputStream.socketRead0(Native Method)
> at java.net.SocketInputStream.read(SocketInputStream.java:152)
> at java.net.SocketInputStream.read(SocketInputStream.java:122)
> at java.net.SocketInputStream.read(SocketInputStream.java:108)
> at
> org.apache.qpid.amqp_1_0.client.Connection.doRead(Connection.java:388)
> at
> org.apache.qpid.amqp_1_0.client.Connection.access$000(Connection.java:47)
> at
> org.apache.qpid.amqp_1_0.client.Connection$2.run(Connection.java:259)
> at java.lang.Thread.run(Thread.java:744)
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
