You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Lorenz Quack (JIRA)" <ji...@apache.org> on 2017/10/03 13:56:01 UTC
[jira] [Updated] (QPID-7951) [Java Broker, AMQP 1.0] Task on
IOThread might cause Config thread to hang indefinitely
[ https://issues.apache.org/jira/browse/QPID-7951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lorenz Quack updated QPID-7951:
-------------------------------
Summary: [Java Broker, AMQP 1.0] Task on IOThread might cause Config thread to hang indefinitely (was: [Java Broker, AMQP 1.0] )
> [Java Broker, AMQP 1.0] Task on IOThread might cause Config thread to hang indefinitely
> ---------------------------------------------------------------------------------------
>
> Key: QPID-7951
> URL: https://issues.apache.org/jira/browse/QPID-7951
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Reporter: Lorenz Quack
> Fix For: qpid-java-broker-7.0.0
>
>
> It seems that it is possible that a Task is submitted to be executed on the IOThread via doOnIOThread but is never being executed because the Connection is already closed. This might result in a Thread hanging indefinetely if it calls ACO.doSync() on the ListeningFuture of the Task.
> This was occurring in the cleanup code to {{TransactionalTransferTest#receiveTransactionalAcquisitionFlowFailsDueToUnknownTransactionId}}.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org