Description of problem:
AutoConnectionCloser class in the ejb remoting API keeps a cache of all remoting connections. These objects are not deleted until the JVM shuts down (this class has a JVM shutdown hook). This causes a memory leak for client applications: particularly multi-threaded ones - in our case, we create a connection for each EJB invocation, which adds up quickly over time.
Version-Release number of selected component (if applicable):
Tested on JBoss EAP 6.2 (module is jboss-ejb-client-1.0.24.Final-redhat-1)
Create a remoting client as described here:
In our case, our client is multi-user/multi-threaded. In high-concurrency/high-throughput test runs, we encounter OutOfMemoryErrors that can be traced back to the org.jboss.remoting3.ConnectionImpl object, which is cached in AutoConnectionCloser
Memory leak of approx. 2k per connection
An option to disable caching would be great!
Is this still valid? The customer case is already closed and indicates that this issue was solved by upgrading to a newer version of the EJB client (1.0.25).
That is correct - issue was resolved by upgrading to 1.0.25.
Bug can be closed.