[ https://issues.apache.org/activemq/browse/AMQCPP-20?page=all ]
Nathan Mittler reopened AMQCPP-20:
----------------------------------
Need to add better handling of close, so that we don't log an error or notify
the client if the broken socket was due to the sending of the stomp disconnect
message (server-initiated socket disconnect).
> Deadlock when in stomp connector close
> --------------------------------------
>
> Key: AMQCPP-20
> URL: https://issues.apache.org/activemq/browse/AMQCPP-20
> Project: ActiveMQ C++ Client
> Issue Type: Bug
> Affects Versions: 1.0
> Reporter: Nathan Mittler
> Assigned To: Nathan Mittler
> Fix For: 1.1
>
>
> When a broken socket occurs, the stomp connector attempts to asynchronously
> close itself. This can cause a deadlock if the main thread is in the close
> method and is performing a join on the transport thread.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
