You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@activemq.apache.org by "Hiram Chirino (Updated) (JIRA)" <ji...@apache.org> on 2012/01/30 13:31:10 UTC
[jira] [Updated] (APLO-140) CPU Spin state using SSL connection,
connections not properly cleaned up.
[ https://issues.apache.org/jira/browse/APLO-140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hiram Chirino updated APLO-140:
-------------------------------
Summary: CPU Spin state using SSL connection, connections not properly cleaned up. (was: Broker get in a bad state not succeeding to remove some connections cleanly)
Updating issue title to reflect symtoms better.
> CPU Spin state using SSL connection, connections not properly cleaned up.
> -------------------------------------------------------------------------
>
> Key: APLO-140
> URL: https://issues.apache.org/jira/browse/APLO-140
> Project: ActiveMQ Apollo
> Issue Type: Bug
> Components: apollo-broker
> Affects Versions: 1.0
> Environment: apollo-1.0-0.20120124.204817.255
> java version "1.6.0_30"
> Java(TM) SE Runtime Environment (build 1.6.0_30-b12)
> Java HotSpot(TM) 64-Bit Server VM (build 20.5-b03, mixed mode)
> Reporter: Massimo Paladin
> Assignee: Hiram Chirino
> Fix For: 1.1
>
> Attachments: 20120127_1408_thread.dump, connections.png, topic_1_10p_0b.xml
>
>
> I can reproduce the problem doing the following:
> - running stomp benchmark with the attached scenario
> - run check_stomp in a loop against the broker on stomp+ssl (check_stomp in this case connect via ssl, drain the destination, send one message and check he receive that message back)
> the check_stomp command line /path..to/check_stomp --config /path/to/file.conf --broker stomp+ssl://host --destination /topic/test.stompssl
> to see what check_stomp does: http://svnweb.cern.ch/guest/MIG/trunk/mig-nagios-plugins/src/check_stomp
> This has as result:
> - very high cpu load remaining after stopping the tests, it remains high until you restart the broker
> - apollo web console reporting some stomp+ssl connections open which are not appearing in netstat at all
> I attach you a thread dump where I am sure that no clients could have been connected.
> nestat output for stomp+ssl port:
> tcp 0 0 0.0.0.0:61133 0.0.0.0:* LISTEN 25699/apollo
> The screenshot about the web console is attached also, it shows the connections remaining in Apollo.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira