[
https://issues.apache.org/jira/browse/QPID-6944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15056290#comment-15056290
]
Mark Soderquist commented on QPID-6944:
---------------------------------------
I think the CPU spike immediately after startup is a bit misleading. Watching
the CPU use and message patterns I'm coming to the conclusion that Qpid 6
simply is using more CPU than it used to when messages come through. The
particular server has pretty consistent, but not overwhelming, traffic going
through it. Once we shut down some of the producers we were able to see that
the CPU spikes are due to messages coming through. I'm just not expecting such
high CPU use for only a few messages.
> 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: 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: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
