Hi, Laird
First, the server is supposed to clean up for the failed deployment
and not the user, but I guess there are some bugs somewhere. :-) If you
have a reproducible case, you could file an issue and we can look into it.
I don't have a complete list of where things should be cleaned up.
But from the error message you got, it seems the application is still
registered in the application registry in memory, so to solve this, the
server probably needs to be restarted.
- Hong
On 4/5/2012 1:52 PM, Laird Nelson wrote:
> I have a situation where someone deployed an .ear file using asadmin
> deploy. It seemed to deploy fine.
>
> Then he undeployed it. This too seemed to work.
>
> asadmin list-applications returns an empty list.
>
> A subsequent asadmin deploy with the same parameters now reports that
> the name is in use. Obviously this cannot be.
>
> In the 3.0.1 days I had a "real world" Glassfish deploy/undeploy
> script that deleted different directories, purged files, cleaned OSGI
> caches, got rid of generated policy files, etc. etc. etc.--all the
> things that aren't supposed to happen but that periodically need to be
> blown away. :-)
>
> Is there a definitive laundry list of such places that can be scrubbed
> clean manually without damaging the server?
>
> Thanks,
> Laird
>
> --
> http://about.me/lairdnelson
>