qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rob Godfrey (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (QPID-6862) IoReceiver thread using CPU even when there are no messages moving
Date Tue, 17 Nov 2015 20:30:10 GMT

    [ https://issues.apache.org/jira/browse/QPID-6862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15009438#comment-15009438

Rob Godfrey commented on QPID-6862:

Hi Mark,

it looks like this is caused by the fact hearbeating / idle timeout detection has not been
fully implemented in AMQP 1.0 for the 0.32 broker.

I'll be attaching a patch to this JIRA in a second which should resolve this issue on 0.32.

We'll shortly be releasing v6.0 of the broker where this issue is already fixed; after that
we are likely to be releasing a 0.32.1 version of the codebase incorporating a number of defect
fixes against the 0.32 codeline which can be backported.

When the 6.0 release candidate comes out (should be in a couple of days), you might want to
do some testing against that in case you find any issues - there's a fair amount of change
vs. 0.32... 

> IoReceiver thread using CPU even when there are no messages moving
> ------------------------------------------------------------------
>                 Key: QPID-6862
>                 URL: https://issues.apache.org/jira/browse/QPID-6862
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Broker
>    Affects Versions: 0.32
>         Environment: Qpid 0.32
> OpenJDK Runtime Environment (build 1.8.0_65-b17)
> Red Hat Enterprise Linux Server release 6.7 (Santiago)
>            Reporter: Mark Soderquist
>         Attachments: QPID-6862.diff
> 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 - / [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 

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org

View raw message