[
https://issues.apache.org/jira/browse/QPID-4170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell updated QPID-4170:
---------------------------------
Attachment: QPID-4170_0.16.patch
Attaching a patch for 0.16, should anyone need to resolve this issue for an
existing system.
It is different than the trunk/0.18 changes because the Queue MBean was
rewritten when moved to the new management-jmx module during 0.18 development.
> JMX threads can spin in the Queue MBean if there is a failure when viewing
> message content
> ------------------------------------------------------------------------------------------
>
> Key: QPID-4170
> URL: https://issues.apache.org/jira/browse/QPID-4170
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: 0.12, 0.13, 0.14, 0.15, 0.16, 0.17
> Reporter: Robbie Gemmell
> Assignee: Robbie Gemmell
> Priority: Critical
> Fix For: 0.18
>
> Attachments: QPID-4170_0.16.patch
>
>
> During the work on QPID-4164 it was found that JMX threads can spin in the
> Queue MBean if they fail when viewing message content, looping down into the
> message and back store asking for content which will never be returned. These
> threads will never stop spinning, and will consume CPU resources and
> introduce additional/unnecessary resource contention within the store layer.
> The view content method of the Queue MBean should be updated to avoid this
> possibility.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]