Hello
This was reported on the Quality mailing list on Friday:
"In the past few days I have been working on Windows 7 with NetBeans,
GlassFish 2.2.1 and Maven. I noticed this behaviour:
When I clean, undeploy and deploy our Enterprise Application with
NetBeans I get file locking errors, while I don't get them when I use
Maven to deploy and undeploy the app. The difference is that I call the
asadmin command from Maven to deploy our ear, while NetBeans uses the
internal deployment to deploy the app. When I clean the app and the
target directory needs to be removed, Maven complains it cannot delete
certain jars since they are in use by another application. Only when I
manually undeploy the ear, or sometimes even only when I stop GlassFish
all together, can the app be cleaned.
Has anyoone else experienced this? I'm not sure if I should report this
issue with GlassFish or with NetBeans."
He used the following tool to diagnose and seems it's Grizzly
http://blogs.sun.com/quinn/entry/tool_for_diagnosing_failed_glassfish
thanks
Richard