activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Endre Stølsvik (JIRA) <j...@apache.org>
Subject [jira] [Updated] (AMQ-5694) ActiveMQTempDestination.delete() can block forever
Date Tue, 31 Mar 2015 00:20:53 GMT

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

Endre Stølsvik updated AMQ-5694:
--------------------------------
    Attachment: thread hangs.png

> ActiveMQTempDestination.delete() can block forever
> --------------------------------------------------
>
>                 Key: AMQ-5694
>                 URL: https://issues.apache.org/jira/browse/AMQ-5694
>             Project: ActiveMQ
>          Issue Type: Bug
>            Reporter: Endre Stølsvik
>         Attachments: thread hangs.png
>
>
> As described in AMQ-5681, we have a setup where we every 10 seconds queries the broker
over JMS for a StatisticsMessage.
> This bug concerns a .. somewhat related .. problem: In that code path, we delete the
temporary reply-to queue after we've read the data.
> We've now several times ended up with a peculiar situation where the thread seems to
have died. Today I grabbed a JMX console and had a look, and the thread is not dead, it is
just locked on the delete call.
> We have another problem with a shared JDBC "cluster" (the "single master, hot standbys"
setup), where the nodes loose master and effectively goes down. What I believe happens, is
that the thread sends the delete message, and then goes into a blocking wait for the reply,
which never appears, probably because the broker that was master and should have sent it,
is now dead.
> The delete code path should probably have had some sane timeout, and just have raised
some JMSException - or something.



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

Mime
View raw message