Bug 1015429 - Cached endpoint never expired
Summary: Cached endpoint never expired
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Remoting
Version: 6.1.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Enrique Gonzalez Martinez
QA Contact: Jitka Kozana
Russell Dickenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-04 08:35 UTC by Hisanobu Okuda
Modified: 2018-12-03 20:10 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-04-10 09:59:32 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Hisanobu Okuda 2013-10-04 08:35:40 UTC
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):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Hisanobu Okuda 2013-10-04 08:38:12 UTC
Need non-cached mode.

Comment 3 Enrique Gonzalez Martinez 2015-04-09 13:47:40 UTC
@Hisanobu:

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 ?

Comment 4 Hisanobu Okuda 2015-04-10 09:33:29 UTC
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.

Comment 5 Enrique Gonzalez Martinez 2015-04-10 09:59:32 UTC
Closing this BZ. See comment#4


Note You need to log in before you can comment on or make changes to this bug.