[
https://issues.apache.org/jira/browse/QPID-6944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Soderquist updated QPID-6944:
----------------------------------
Attachment: qpid.log.zip
I'm back from vacation. I applied the patch and captured a high CPU event
around the time 2016-01-05 14:25:30.
> High CPU use sending message using SSL
> --------------------------------------
>
> 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
> Assignee: Keith Wall
> Attachments: SelectorThread.patch, broker.acl, config.json,
> config.json, default.json, enabledebug.png, qpid.0.32.png, qpid.6.0.png,
> qpid.cpu.png, qpid.cpu.png, qpid.log.zip, qpid.log.zip, qpid6944.zip,
> threaddump-1449856663270.tdump, virtualhosts.xml
>
>
> Qpid is experiencing high CPU use when a message is sent. While the
> application still functions it causes the CPU to run at nearly 100%. This has
> been narrowed down to enabling SSL on the AMQP port. With SSL disabled there
> is normal CPU use, but with it enable the CPU use spike when messages are
> received or consumed.
--
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
