Re: ClassNotFoundError on context unload

> > Please file a bug in Bugzilla for this. If you're feeling > enterprising, go ahead and attach a WAR (including source) that can > reproduce the issue. Submitted as bug 57772 . The example WAR is on github, and the steps to reproduce should

Re: ClassNotFoundError on context unload

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Austin, On 3/26/15 7:33 PM, Austin Jones wrote: > I believe I figured this part out in the debugger. When the > WebappClassLoader attempts to load the class, the .class file (and > the entire exploded directory) is not on the disk. First, let me

Re: ClassNotFoundError on context unload

Hi Chris, I know what is going on here (it is quite clear in the debugger). I'll take you through it one step at a time in this email, but the issue is complicated, so I'll try to be thorough. Would you be willing to try the newly-minted 8.0.21, or 8.0.20, to see if it makes a difference? Yes,

Re: ClassNotFoundError on context unload

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Austin, On 3/23/15 2:54 PM, Austin Jones wrote: > Hi Chris, > >> If MyClass had been loaded at initialization time (like your >> sample code shows), it should not have needed to be loaded back >> off the disk for shutdown. > > In my first example,

Re: ClassNotFoundError on context unload

Hi Chris, > If MyClass had been loaded at initialization time (like your sample > code shows), it should not have needed to be loaded back off the disk > for shutdown. In my first example, the ClassNotFoundError is thrown when enabled=false. When enabled=true, the error doesn't occur. Is it poss

Re: ClassNotFoundError on context unload

Hi Mark, Sorry for the ambiguous 'unload' language, I suppose the tomcat language would be 'context stop'. The issue occurs when deploying the WAR using the Tomcat Manager interface (*not *by dropping the WAR in /webapps). You should be able to reproduce the issue with these steps: 1. Build t

Re: ClassNotFoundError on context unload

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Austin, On 3/22/15 10:11 PM, Austin Jones wrote: > After a bit of debugging, I found the issue. The stack traces > below are on 8.0.12-src. > > The bug occurs at this stack: > >> StandardContext.reload() line: 3779 >> HostConfig.reload(HostConfi

Re: ClassNotFoundError on context unload

On 23/03/2015 02:11, Austin Jones wrote: > After a bit of debugging, I found the issue. The stack traces below are on > 8.0.12-src. > > The bug occurs at this stack: > >> StandardContext.reload() line: 3779 >> HostConfig.reload(HostConfig$DeployedApplication) line: 1306 >> HostConfig.checkResour

Re: ClassNotFoundError on context unload

After a bit of debugging, I found the issue. The stack traces below are on 8.0.12-src. The bug occurs at this stack: > StandardContext.reload() line: 3779 > HostConfig.reload(HostConfig$DeployedApplication) line: 1306 > HostConfig.checkResources(HostConfig$DeployedApplication) line: 1238 > HostC

Re: ClassNotFoundError on context unload

I was able to reproduce the issue in a simple testcase application: https://github.com/austinjones/ClassNotFoundGenerator/ On Sun, Mar 22, 2015 at 1:45 PM, Austin Jones wrote: > I put 8.0.20 on a testing machine, and saw the same issue. > > On Sun, Mar 22, 2015 at 12:15 PM, Christopher Schultz <

Re: ClassNotFoundError on context unload

I put 8.0.20 on a testing machine, and saw the same issue. On Sun, Mar 22, 2015 at 12:15 PM, Christopher Schultz < ch...@christopherschultz.net> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Austin, > > On 3/21/15 6:19 PM, Austin Jones wrote: > > I'm having an issue with Tomcat 8

Re: ClassNotFoundError on context unload

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Austin, On 3/21/15 6:19 PM, Austin Jones wrote: > I'm having an issue with Tomcat 8.0.12 when undeploying contexts. > I have autoDeploy turned off, and am pushing WARs+context.xmls > through the Tomcat manager's deploy command. > > I have several S

ClassNotFoundError on context unload

I'm having an issue with Tomcat 8.0.12 when undeploying contexts. I have autoDeploy turned off, and am pushing WARs+context.xmls through the Tomcat manager's deploy command. I have several ServletContextListeners that handle proper context shutdown. The ones that cause the issue look like this: