[ 
https://issues.apache.org/jira/browse/QPID-6862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Keith Wall closed QPID-6862.
----------------------------
       Resolution: Fixed
    Fix Version/s: qpid-java-6.0

> 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
>            Assignee: Rob Godfrey
>             Fix For: qpid-java-6.0
>
>         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 - /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 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to