[QPID-6862] IoReceiver thread using CPU even when there are no messages moving

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.32
• Fix Version/s: qpid-java-6.0
• Component/s: Broker-J

Environment

Qpid 0.32
OpenJDK Runtime Environment (build 1.8.0_65-b17)
Red Hat Enterprise Linux Server release 6.7 (Santiago)

• Assignee: Robert Godfrey
• Reporter: Mark Soderquist
• Created: 16/Nov/15 22:34
• Updated: 05/May/16 21:10
• Resolved: 05/May/16 21:10

Description

On our Qpid server we have roughly 25 connections to the server. The traffic over these connections is very light (1 msg/5 mins). However, the IoReceiver threads are constantly using around 3% CPU each, causing approximately 75% CPU use. We don't understand why the IoReceiver threads are using CPU when there are very few messages moving. Here is a stack trace of one of the IoReceiver threads:

Stack Trace
IoReceiver - /10.118.252.6:59297 [169442] (RUNNABLE)
java.net.SocketInputStream.socketRead0 line: not available [native method]
java.net.SocketInputStream.socketRead line: 116
java.net.SocketInputStream.read line: 170
java.net.SocketInputStream.read line: 141
sun.security.ssl.InputRecord.readFully line: 465
sun.security.ssl.InputRecord.read line: 503
sun.security.ssl.SSLSocketImpl.readRecord line: 973
sun.security.ssl.SSLSocketImpl.readDataRecord line: 930
sun.security.ssl.AppInputStream.read line: 105
org.apache.qpid.transport.network.io.IoReceiver.run line: 156
java.lang.Thread.run line: 745

Issue Links

• relates to: QPID-6843 [Java Broker] Implement Broker side heartbeating in 1.0 AMQP implementation