Hi, Todd.
You are probably undeploying the app just fine.
The problem seems to be that the framework you are using has opened a stream as it ran but never closed it.
Although the error message may seem alarming, it is actually reporting good news. The class loader that GlassFish uses has detected that the stream was left open and is closing it even though the framework (in this case) did not do so. (Internally when an app is undeployed GlassFish tells the class loader for the app that it should clean up, and this is part of that clean-up.)
That keeps the process from consuming open file channels and, on Windows (which does not look like it applies in your case) allows the JAR file to which that stream had been opened to be deleted or renamed, something Windows prohibits if a file is open.
You could see about opening an issue for the framework, pointing out the stream that seems to be left open. (The stack trace helps to pinpoint where the stream was opened, which could be different of course from what code should close it!)
- Tim
[Message sent by forum member 'tjquinn' (tjquinn)]
http://forums.java.net/jive/thread.jspa?messageID=269298