You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Mark Soderquist (JIRA)" <ji...@apache.org> on 2015/12/15 18:31:46 UTC
[jira] [Commented] (QPID-6944) High CPU use sending message
[ https://issues.apache.org/jira/browse/QPID-6944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15058383#comment-15058383 ]
Mark Soderquist commented on QPID-6944:
---------------------------------------
I have attached a project that is duplicating the issue.
1. We are using the qpid-amqp-1-0-client 0.32 libraries.
2. The messages are usually small. The test client I attached sends 20 byte messages but the issue is clearly visible in the CPU spikes. Transactions are not in use. I also noticed that the issue can be reproduced by just sending a message without consuming it.
3. Here are the log lines with versions and memory use:
2015-12-10 07:25:12,936 INFO [main] (broker.startup) - [Broker] BRK-1001 : Startup : Version: 0.32 Build: Unversioned directory
2015-12-10 07:25:12,943 INFO [main] (broker.platform) - [Broker] BRK-1010 : Platform : JVM : Oracle Corporation version: 1.7.0_91-mockbuild_2015_10_20_10_42-b00 OS : Linux version: 2.6.32-573.8.1.el6.x86_64 arch: amd64
2015-12-10 07:25:12,950 INFO [main] (broker.max_memory) - [Broker] BRK-1011 : Maximum Memory : 2,138,767,360 bytes
I think it is important to note that we are using the Berkeley DB for persistence. We have used both versions 6.2.31 and 6.4.9 with the same CPU spike results.
We also tried using Java 7 instead of Java 8 with the same CPU spike results.
> High CPU use sending message
> ----------------------------
>
> 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: enabledebug.png, qpid.0.32.png, qpid.6.0.png, qpid.cpu.png, qpid.cpu.png, qpid6944.zip, 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-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org