GFv3.1.2 Domain Installed on a NFSv3 Mount Point, Undeploying an Application Leaves .nfs and .glassfishStaleFiles Files Behind
(Doc ID 2043390.1)
Last updated on NOVEMBER 05, 2016
Applies to:Oracle GlassFish Server - Version 3.1.2 to 3.1.2 [Release 3.1]
When a Glassfish Domain is configured on a NFSv3 network mount, then within some environments an asadmin undeploy command can leave .glassfishStaleFiles and .nfsxxx files (where xxx is some string of characters) behind on the NFS mount. This will cause an failure of the next asadmin deploy command when the same application is deployed again.
This issue is not seen on every NFSv3 environment and seems a rare or random or network slowness behavior.
Glassfish v3.1.2 installed on a NFSv3 mounted filesystem.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document