You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Adam Sussman (JIRA)" <ji...@apache.org> on 2010/12/08 01:54:02 UTC
[jira] Created: (AMQ-3074) Expose TransportConnection.stopping
Expose TransportConnection.stopping
-----------------------------------
Key: AMQ-3074
URL: https://issues.apache.org/jira/browse/AMQ-3074
Project: ActiveMQ
Issue Type: Improvement
Components: Broker
Affects Versions: 5.4.2
Reporter: Adam Sussman
Priority: Minor
Pleas expose the boolean broker.TransportConnection.stopping.
When an exception occurs on a TransportConnection (aka client closes or drops connection to server), there is no visibility into the fact that the connection is broken until the async stop process stops. Often this gets delayed by other processing. The 'stopping' variable gets set immediately on exception and so processes that are doing work with the connection can check it and get immediate feedback.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (AMQ-3074) Expose TransportConnection.stopping
Posted by "Adam Sussman (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQ-3074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Adam Sussman updated AMQ-3074:
------------------------------
Attachment: amq-3074.patch
> Expose TransportConnection.stopping
> -----------------------------------
>
> Key: AMQ-3074
> URL: https://issues.apache.org/jira/browse/AMQ-3074
> Project: ActiveMQ
> Issue Type: Improvement
> Components: Broker
> Affects Versions: 5.4.2
> Reporter: Adam Sussman
> Priority: Minor
> Attachments: amq-3074.patch
>
>
> Pleas expose the boolean broker.TransportConnection.stopping.
> When an exception occurs on a TransportConnection (aka client closes or drops connection to server), there is no visibility into the fact that the connection is broken until the async stop process stops. Often this gets delayed by other processing. The 'stopping' variable gets set immediately on exception and so processes that are doing work with the connection can check it and get immediate feedback.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] [Resolved] (AMQ-3074) Expose TransportConnection.stopping
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQ-3074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Bish resolved AMQ-3074.
-------------------------------
Resolution: Fixed
Fix Version/s: 5.6.0
Assignee: Timothy Bish
Don't see any harm in exposing this so I applied the patch. Thanks.
> Expose TransportConnection.stopping
> -----------------------------------
>
> Key: AMQ-3074
> URL: https://issues.apache.org/jira/browse/AMQ-3074
> Project: ActiveMQ
> Issue Type: Improvement
> Components: Broker
> Affects Versions: 5.4.2
> Reporter: Adam Sussman
> Assignee: Timothy Bish
> Priority: Minor
> Fix For: 5.6.0
>
> Attachments: amq-3074.patch
>
>
> Pleas expose the boolean broker.TransportConnection.stopping.
> When an exception occurs on a TransportConnection (aka client closes or drops connection to server), there is no visibility into the fact that the connection is broken until the async stop process stops. Often this gets delayed by other processing. The 'stopping' variable gets set immediately on exception and so processes that are doing work with the connection can check it and get immediate feedback.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira