You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Tommy Lillehagen (JIRA)" <ji...@apache.org> on 2017/12/14 15:24:00 UTC

[jira] [Created] (ARTEMIS-1559) Repeated retries of unencrypted traffic to SSL-enabled boker causes OOM exception

Tommy Lillehagen created ARTEMIS-1559:
-----------------------------------------

             Summary: Repeated retries of unencrypted traffic to SSL-enabled boker causes OOM exception
                 Key: ARTEMIS-1559
                 URL: https://issues.apache.org/jira/browse/ARTEMIS-1559
             Project: ActiveMQ Artemis
          Issue Type: Bug
    Affects Versions: 2.4.0, 2.3.0
            Reporter: Tommy Lillehagen


Repro steps:

 * We have a broker (A) set up with SSL enabled (using Artemis v2.4 / v2.3)
 * A client (B) set up to use plain (non-TLS) communication (same version of Artemis)
 * Trying to establish a connection between (B) and (A) triggers multiple retries
 * Each message gets, from what I can tell, rejected quickly by (A), but each iteration leaks heap memory
 * Due to the number of retries in a short amount a time (~1000s from what I can tell) causes the above to grow the heap by 470M or so within less than 10 seconds (the set timeout)
 * This consequently results in an out of memory exception

The above behaviour is observed in both version 2.3 and 2.4.

We've tested older versions (2.1 and 2.2), and neither of those manifest the same problem.

I've run some profiling on (A), and {{NettyAcceptor.initChannel}} ({{getSslHandler()}}) seems to be a critical point (will include screenshots).

That being said, most of the accumulated heap memory seems to be claimable and is mostly collected during the next GC cycle in the tests that I've run.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)