Skip to content
This repository has been archived by the owner on Jan 30, 2019. It is now read-only.

Memory leak in WSITServerAuthConfigProvider with WSITServerAuthConfig #1655

Open
glassfishrobot opened this issue Sep 20, 2012 · 6 comments
Open

Comments

@glassfishrobot
Copy link
Contributor

The WSITServerAuthConfigProvider keeps instances of WSITServerAuthConfig in the WeakHashMap serverConfigMap.

The key (referent) to preserve the instances of WSITServerAuthConfig is a String instance which is also used as member appContext in instances of WSITServerAuthConfig.

This creates a reference loop, thus creates memory leaks: Undeployed applications aren't freed.

Environment

glassfish 3.1.2
any jdk
any os

@glassfishrobot
Copy link
Contributor Author

Reported by bebbo

@glassfishrobot
Copy link
Contributor Author

Was assigned to snajper

@glassfishrobot
Copy link
Contributor Author

snajper said:
Thanks, do you have a sample app for this? Which WSITServerAuthConfigProvider is this about?

@glassfishrobot
Copy link
Contributor Author

bebbo said:
package com.sun.xml.wss.provider.wsit;

I can't post our ear - let's see if I can provide a minimal example.

Any ear should work as long it uses a secure realm (e.g. using ldap).

@glassfishrobot
Copy link
Contributor Author

ymajoros said:
http://www.franke.ms/#glassfish-memory-leak.wiki seems to have a patch for this

@glassfishrobot
Copy link
Contributor Author

This issue was imported from java.net JIRA WSIT-1655

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant