I might not have had anything to do with that. I have seen poorly written
applications - for example one which falls into an infinite loop condition
in a Startup servlet, under Glassfish v2.x hang on deployment. You can check
the server.log or your the log(s) of the application you deployed to see if
that was the issue. If you run into something like that you basically have
to manually undeploy the application by stopping Glassfish (usually have to
kill the java.exe process it is running under using TaskManager on windows
or kill -9 on Unix/Linux) the go into the domain directory for the domain it
was deployed to and remove all the generated directories/files that belonged
to it under the generated directory and remove and references to the
Application from the domain.xml file in the conf directory. Then you have to
fix the application so it doesn't happen again.
-Noah
On Thu, Nov 19, 2009 at 7:38 AM, <glassfish_at_javadesktop.org> wrote:
> i couldn't find wat the root cause was. but probably some file got
> corrupted after my server crashed for the first time. all i did was
> uninstall the app server that is glassfish completely and then install it
> again. fresh and clean. now it's working fine..
> [Message sent by forum member 'eakangk' ]
>
> http://forums.java.net/jive/thread.jspa?messageID=372543
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>
>