Bug 1015429

Summary:	Cached endpoint never expired
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	Hisanobu Okuda <hokuda>
Component:	Remoting	Assignee:	Enrique Gonzalez Martinez <egonzale>
Status:	CLOSED NOTABUG	QA Contact:	Jitka Kozana <jkudrnac>
Severity:	unspecified	Docs Contact:	Russell Dickenson <rdickens>
Priority:	unspecified
Version:	6.1.1	CC:	bmaxwell, cdewolf, egonzale, jamie.beznoski
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-04-10 09:59:32 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

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