You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@geronimo.apache.org by ericp56 <er...@twcable.com> on 2010/02/08 20:46:38 UTC
G2.2 Unable to clear Sun JarFileFactory cache
What's the best course of action for
http://issues.apache.org/jira/browse/GERONIMO-5036
http://issues.apache.org/jira/browse/GERONIMO-5036 ?
1) Keep using update 18 - it won't affect your applications.
2) Use JDK 1.6 Release 1.6_0_???
3) Update OpenEjb to ???
4) Other?
Please advise.
Thanks!
Eric
--
View this message in context: http://old.nabble.com/G2.2--Unable-to-clear-Sun-JarFileFactory-cache-tp27505204s134p27505204.html
Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
Re: G2.2 Unable to clear Sun JarFileFactory cache
Posted by ericp56 <er...@twcable.com>.
Thanks!
--
View this message in context: http://old.nabble.com/G2.2--Unable-to-clear-Sun-JarFileFactory-cache-tp27505204s134p27577095.html
Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
Re: G2.2 Unable to clear Sun JarFileFactory cache
Posted by Kevan Miller <ke...@gmail.com>.
On Feb 8, 2010, at 2:46 PM, ericp56 wrote:
>
> What's the best course of action for
> http://issues.apache.org/jira/browse/GERONIMO-5036
> http://issues.apache.org/jira/browse/GERONIMO-5036 ?
>
> 1) Keep using update 18 - it won't affect your applications.
> 2) Use JDK 1.6 Release 1.6_0_???
> 3) Update OpenEjb to ???
> 4) Other?
>
> Please advise.
1) Ignore. You should not see any functional problems. You may see a ClassLoader memory leak -- which after repeated deploy/undeploy cycles could result in a PermGen OutOfMemoryError. Hmm. Actually, this may be trying to avoid jar files being locked on Windows -- which would prevent the jar files from being deleted from your hard-drive. Either way, I don't expect anything too serious.
3) You can apply the patch to OpenEJB and update the OpenEJB jars in your geronimo installation.
We should have this fixed in a 2.1.5 and 2.2.1 release...
--kevan