[
https://issues.apache.org/jira/browse/QPID-6944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15057978#comment-15057978
]
Keith Wall commented on QPID-6944:
----------------------------------
Hi Mark
Glad to hear the lock wasn't a Java Broker issue. Could you update the jira
title to capture the remaining issue precisely?
I've done some testing this morning hoping to reproduce your issue. No luck so
far. I don't see CPU spiking to 100% during long running cycles of
publication/consuming.
Could you let me know:
# Which Qpid client you use? which version? I think you use
{{o.a.q:qpid-amqp-1-0-client-jms}} rather than {{o.a.q:qpid-jms-client}}, but
want to be sure.
# What is the approximate JMS message size and persistence setting? Are
transactions in use?
# What heap size and direct memory size are in use? (BRK-1011 report both on
startup)
If you have a small JMS program that reproduces the issue, that would be very
useful.
Also, it might also be informative to turn up logging level for org.apache.qpid
to DEBUG whilst the issue manifest. See attached screenshot.
> SelectorThread causing livelock
> -------------------------------
>
> Key: QPID-6944
> URL: https://issues.apache.org/jira/browse/QPID-6944
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: qpid-java-6.0
> Environment: Red Hat Enterprise Linux Server release 6.7 (Santiago)
> OpenJDK Runtime Environment (build 1.8.0_65-b17)
> OpenJDK 64-Bit Server VM (build 25.65-b01, mixed mode)
> Reporter: Mark Soderquist
> Attachments: qpid.0.32.png, qpid.6.0.png, qpid.cpu.png, qpid.cpu.png,
> threaddump-1449856663270.tdump
>
>
> The org.apache.qpid.server.transport.SelectorThread is causing live lock.
> While the application still functions it causes the CPU to run at nearly
> 100%. See attached thread dump.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
