Red Hat Bugzilla – Bug 1015429
Cached endpoint never expired
Last modified: 2015-04-13 09:35:24 EDT
Description of problem:
Properties for remoting connection are cached in org.jboss.naming.remote.client.EndpointCache.cache, and never be removed until JVM shutdown. It causes memory leak when many authentications with different endpoint.name performed
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Need non-cached mode.
Just having a look at this it seems that NamingStoreCache is not cleaning up the endpoint when a naming store is removed from the cache.
Is it possible to know how are you setting up the remote connection ?
Enrique, thank you for picking up this. The original issue in the support case is that a cached username/password is not updated within a endpoint in EAP 6.1.0. I confirmed it is fixed in EAP 6.1.1. Therefore, the scenario that you need to use a lot of endpoints for a lot of users is not considerable now. The cache is not cleaned up even now, but it is not an issue for now. You can close this BZ.
Closing this BZ. See comment#4