[jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1637) Interruption is busted
Tim Fox (JIRA)
jira-events at lists.jboss.org
Tue Jun 2 05:24:56 EDT 2009
[ https://jira.jboss.org/jira/browse/JBMESSAGING-1637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12470188#action_12470188 ]
Tim Fox commented on JBMESSAGING-1637:
--------------------------------------
Where does this originally come from?
I'm guessing it's because the new AS console has a (new) requirement that all component operations need to be interruptible? If so, we can deal with that, but I wouldn't expect all operations, especially in the older 1.x code base to allow ops to be interrupted.
We've never made the claim that our operations are interruptible.
> Interruption is busted
> ----------------------
>
> Key: JBMESSAGING-1637
> URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1637
> Project: JBoss Messaging
> Issue Type: Bug
> Components: Messaging Core
> Affects Versions: 1.4.1.GA, 1.4.3.GA
> Reporter: David Lloyd
> Assignee: Howard Gao
> Fix For: 1.4.5.GA
>
> Attachments: fix-interruption.patch
>
>
> Interruption handling is way wrong in MessagingPostOffice. Attaching a patch that at least prevents large amounts of exception spewage when a JBM thread is interrupted. Please check it over and apply.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list