|
|
|
|
|
If you are using GlassFish on Windows and are deploying via archives (like EAR, a WAR, an EJB JAR, or an app client JAR) you may have encountered a variation of GlassFish Issue 539 where a problem during deployment leads to a locked JAR that requires a server restart. The good news is that Tim and Hong have checked in changes to address this problem: when possible the problem no longer occurs and, when it does, there is a nice error message that leads to a prompt resolution. |
Expect the fix in the next promotion of GlassFish V2. Check Tim's Blog for a detailed description of the problem and the solution.
