RE: [WDSCI-L] Now for something completely different...

["Joe Pluta" <joepluta@xxxxxxxxxxxxxxxxx>]

> From: colin williams
> 
> Joe,
> 
> I think the loading and unloading of classes, and their dependencies,
> - Static variables
> - Static initializers
> - Native methods
> 
> is dependent on the classloader that loaded it.
> 
> That would lead me to think that any class, and hence static
initializers
> loaded by a specific web application classloader, will be unloaded
when
> any
> references to that classloader are removed. Presumably stopping a web
> application does this.

>From my empirical testing it looks as though the following occurs:

Classes are unloaded
Statics are thus reinitialized

However, the native methods are not completely cleaned up.
Specifically, it looks as though the service program that the Java
Toolkit talks to is not released (QSYS/QYJSPART).  The newly started
application cannot load the service program ("it is already loaded in
another classloader") and so gets an UnsatisfiedLink error and dies.

Not particularly helpful.

Joe