Performing leak analysis shows that the following internal TLS classes are leaked, once per TLS connection, when connecting using the Qpid JMS Client 0.26.0 over AMQP 1.0 with TLS. The same leak was not apparent when connecting the older Qpid JMS AMQP 0-x client.
The classes are:
The test is run with the following command:
It seems there is session caching going on within the JDK. The cache size and timeout looks to be tuneable with javax.net.ssl.SSLContext#getServerSessionContext. The default timeout is 86400s (1day) and a session cache size of 0 (unbounded). I suspect if Broker had a sufficiently large number of TLS connections over a short time period, memory may be exhausted.
I don't currently understand why the behaviour is different between the old/new JMS client. Edit - see comment below.