Thanks for the tip, I didn't know about this utility.
From the command's output, it seems like the app server is not running - the
only listed line is the JPS utility itself.
Instead of using the Windows service, I tried using the asadmin.bat command
line. start-domain fails with a generic "Domain domain1 failed to startup"
message. The server.log file contains the following errors:
IOP00410216: (COMM_FAILURE) Unable to create IIOP listener on the specified
host/port: all interfaces/3700
org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 216 completed: No
[...]
Caused by: java.net.BindException: Address already in use: bind
So someone is already using this port. Is it a past instance of Glassfish
that didn't shut down correctly or another process, I don't know.
I then try a stop-domain, which fails with a "The domain (domain1) isn't
running".
Any idea how I can identify who's using this port?
Thanks again,
GB
Binod.Pg wrote:
>
> Can you use jps -l to find which process is appserver?
>
> - Binod.
>
>>Salut JF,
>>
>>I added this line, but the thing is I cannot even restart the server since
I
>>have no handle on it! Don't know which process it is so can't kill it,
and
>>the Windows (2000 Server) service is shown as being stopped.
Unfortunately
>>I cannot reboot the server right now since it's used by other
applications.
>>That's why I'm looking for some sort of force shutdown.
>>
>>Merci!
>>GB
>>
>>
>>
>>Jean-Francois Arcand wrote:
>>
>>
>>>Salut Guillaume,
>>>
>>>Can you add
>>>
>>><jvm-options>-Dcom.sun.enterprise.server.ss.ASQuickStartup=false</jvm-options>
>>>
>>>in file ${glassfish.home}/domains/domain1/config/domain.xml
>>>
>>>and see if the problem occurs (I suspect the problem will disappear). I
>>>suspect your firewall and or anti-virus and AsyncStartup have some
>>>conflicts.
>>>
>>>A+
>>>
>>>-- Jeanfrancois
>>>
>>>
>>>Guillaume Bilodeau wrote:
>>>
>>>
>>>>Hi guys,
>>>>
>>>>Since a few days I'm experiencing some problems with my GlassFish (SJSAS
>>>>9.0.0) server. One problem is that, for some unknown reason, it stops
>>>>responding (no response when trying to open the URL to a deployed
>>>>application or the management console). Another problem is that
shutting
>>>>it
>>>>down constantly fails, both through the Windows service stop or the
>>>>manual
>>>>asadmin stop-server command line call. And since it seems to be running
>>>>in
>>>>one of the java.exe processes, and there are many of them running right
>>>>now,
>>>>I cannot just end the process manually.
>>>>
>>>>There is nothing suspicious in the server logs. The only thing I can
>>>>think
>>>>of is that it's running on a crowded server and there might be some
other
>>>>program that's somehow messing up with the resources.
>>>>
>>>>Is there any way to force GlassFish to shut down? And is there any
other
>>>>place I could look for any trace of a potential problem?
>>>>
>>>>Thanks,
>>>>GB
>>>>
>>>>
>>>>
>>>---------------------------------------------------------------------
>>>To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
>>>For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>
>
>
--
View this message in context: http://www.nabble.com/Forcing-shutdown--tf2428720.html#a6791820
Sent from the java.net - glassfish users mailing list archive at Nabble.com.