I have a web-application in which classloader leaks when application is redeployed. Among others there's a reference from TransientFileFactory's shutdown hook to unloaded classloader, so this is a 'real world issue' :) I'm trying to resolve it, that's why I'm asking about TransientFileFactory leaking. Thanks for your suggestion about using shared jcr-commons, but for our application we're trying to deploy all used libraries inside our WAR, so shared library is undesirable.
Stefan Guggisberg-2 wrote: > > On Wed, May 28, 2008 at 12:33 PM, Roman Puchkovskiy > <[EMAIL PROTECTED]> wrote: >> >> Hi. >> >> Some classes in Jackrabbit (for instance, TransientFileFactory) always >> register shutdown hooks. So, if jackrabbit classes were loaded by web-app >> classloader, they will not be released when web-app is undeployed. Looks >> like this should lead to classloader leak. >> Am I missing something? And if this causes leaks, is there way to cancel >> such hooks when undeploying web-application? > > is this a pure theoretical issue or have you actually experienced > "out of perm space" errors? > > i agree with your analysis that the addShutdownHook call in > TransientFileFactory is a potential classloader related memory > leak. however, so far i haven't heard of any "out of perm space" > reports. > > OTOH, if this is a real world issue we should probably address it. > > BTW: TransientFileFactory is part of jcr-commons which could/should > be deployed as a shared library. > > cheers > stefan > >> >> Thanks in advance. >> -- >> View this message in context: >> http://www.nabble.com/Shutdown-hooks-and-classloader-leak-tp17509737p17509737.html >> Sent from the Jackrabbit - Users mailing list archive at Nabble.com. >> >> > > -- View this message in context: http://www.nabble.com/Shutdown-hooks-and-classloader-leak-tp17509737p17512481.html Sent from the Jackrabbit - Users mailing list archive at Nabble.com.
