[
https://issues.apache.org/jira/browse/AMQ-4532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-4532.
-----------------------------
Resolution: Fixed
fix in http://svn.apache.org/r1482117
> shutdown of VMTransportServer should report disposed exception to peer
> pending requests
> ---------------------------------------------------------------------------------------
>
> Key: AMQ-4532
> URL: https://issues.apache.org/jira/browse/AMQ-4532
> Project: ActiveMQ
> Issue Type: Bug
> Components: Transport
> Affects Versions: 5.8.0
> Reporter: Gary Tully
> Assignee: Gary Tully
> Labels: asyncRequest, shutdown, vmtransport
> Fix For: 5.9.0
>
>
> When a broker is shutdown all transport connectors are shutdown ok. However a
> vm client with pending asyncRequests does not get a notification of the peer
> (server in this case) shutdown and waits for ever.
> This is noticeable in camel routes that do graceful shutdown from a shutdown
> hook when there are pending requests.
> The current shutdown/stop logic sends a shutdowninfo which works fine when
> the client initiates the stop but shutdown in not processed by a client.
> A simple fix is to propagate a shutdown/disposed exception that clients will
> respond to and error out any pending futures.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
