activemq-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hiram Chirino (Updated) (JIRA)" <>
Subject [jira] [Updated] (APLO-140) CPU Spin state using SSL connection, connections not properly cleaned up.
Date Mon, 30 Jan 2012 12:33:10 GMT


Hiram Chirino updated APLO-140:

    Affects Version/s:     (was: 1.0)
        Fix Version/s:     (was: 1.1)
> CPU Spin state using SSL connection, connections not properly cleaned up.
> -------------------------------------------------------------------------
>                 Key: APLO-140
>                 URL:
>             Project: ActiveMQ Apollo
>          Issue Type: Bug
>          Components: apollo-broker
>         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.0
>         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
> the check_stomp command line / --config /path/to/file.conf --broker
stomp+ssl://host --destination /topic/test.stompssl
> to see what check_stomp does:
> 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     *                   LISTEN  
> 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:!default.jspa
For more information on JIRA, see:


View raw message