Skip to main content

Toplink & undeploy file locking

2 replies [Last post]
sbalmos
Offline
Joined: 2006-08-02

Hi all,

This is most likely related to the on and off discussions going on here concerning JARs that are unable to be deleted during an undeploy or redeploy. At least in my particular case, on Windows using v2b16, it seems isolated to Toplink. The only JAR that GF is unable to undeploy or generally delete (until the server instance is shut down) is my persistent entity JAR.

Just an FYI, comments from others, etc.

--Scott

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
tjquinn
Offline
Joined: 2005-03-30

Hi, Scott.

In some of the other conversations about locked JARs I've referred to a tool - simple and unpolished but effective - that you can use to help identify the code that opens but does not close the offending JARs.

Here's a link to a blog entry that describes how to use the tool and where to download it:

http://blogs.sun.com/quinn/entry/tool_for_diagnosing_failed_glassfish

If you have a chance, please try it in your environment and either post the results here or e-mail them to me. This will help us decide if this is a bug that we can fix or an artifact of the way locked files on Windows are handled. Even in the second case we are working on some changes in GlassFish that will lessen the severity of the problem.

Thanks.

- Tim

tjquinn
Offline
Joined: 2005-03-30

I am glad to report that we have checked in some changes to GlassFish that will help a great deal with this sort of problem. Those changes and the improved behavior of GlassFish from a user's perspective are described here http://blogs.sun.com/quinn/entry/addressing_locked_jar_problems for anyone interested.

The changes should be in build 22 (next week). It would be interesting to know if that build handles this app better.

- Tim