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.