Prakasam created AMQ-7285:
-----------------------------
Summary: ActiveMQConnection.deleteTempDestination() is not resumed
after the AMQ restart also but ActiveMQSession.deleteTempDestination is not.!
Key: AMQ-7285
URL: https://issues.apache.org/jira/browse/AMQ-7285
Project: ActiveMQ
Issue Type: Bug
Components: Transport
Affects Versions: 5.13.0
Reporter: Prakasam
Hi,
We have identified the Thread Blocking during the deletion of Temporary Topic.
Scenario:
# We have a setup of Request-Reply Mode using the temporary destinations.
# The Server hit No space memory and ActiveMQ is also stuck with that. During
this time the broker also fails to connect with the client. Checked the
Threads. Both .send() and delete() was waiting for the connection. It was stuck
ar .syncSendpacket().
{quote}at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
at
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039)
at java.util.concurrent.ArrayBlockingQueue.take(ArrayBlockingQueue.java:403)
at
org.apache.activemq.transport.FutureResponse.getResult(FutureResponse.java:48)
at
org.apache.activemq.transport.ResponseCorrelator.request(ResponseCorrelator.java:87)
at
org.apache.activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnection.java:1381)
{color:#172b4d} 3. We have restarted our ActiveMQ then after few minutes .
The AMQ is reconnected successfully. Then We have found that the thread
blocking again. The thread dump revelas that .deleteTempDestination is still
waiting for the connection while .send() is resumed properly when it is
reconnected with the broker.{color}
{color:#172b4d}Broker URI :
failover:(nio://localhost:61616?wireFormat.maxInactivityDuration=120000){color}
{quote}
{color:#172b4d}Thanks,{color}
{color:#172b4d}Prakasam{color}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
