[
https://issues.apache.org/jira/browse/QPID-6944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Soderquist updated QPID-6944:
----------------------------------
Attachment: config.json
This morning I think I was able to narrow down the issue. I started with a
vanilla installation and configuration, then started adding custom
configuration until I could reproduce the problem. Luckily it didn't take much.
As soon as I switched the AMQP port to use SSL I started getting high CPU use.
I have attached the config.json that I used to reproduce the issue. I think the
only things I had to change were the password file location, the RMI and JMX
ports and the AMQP security.
> 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
> 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, qpid6944.zip,
> threaddump-1449856663270.tdump, virtualhosts.xml
>
>
> 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]
