[jboss-jira] [JBoss JIRA] Closed: (JBAS-5468) when the shutdown of the server is complete, some ports still been used (timing issue)
Adrian Brock (JIRA)
jira-events at lists.jboss.org
Tue Apr 22 06:31:46 EDT 2008
[ http://jira.jboss.com/jira/browse/JBAS-5468?page=all ]
Adrian Brock closed JBAS-5468.
------------------------------
Resolution: Rejected
This is NOT a JBoss issue.
1) When JBoss shutdowns it tells the Coyote connection to stop which closes the port
2) The "HALT" shown terminates the process which means the OS should close the port
anyway (even if JBoss didn't do it explictly).
To test JBoss is doing it correctly, I chose the harder problem of undeploying JBossWeb
on a running server. i.e. not process termination to catch a missing ServerSocket.close()
[ejort at warjort bin]$ cd ../server/default/deploy/
[ejort at warjort deploy]$ mv jboss-web.deployer/ ~/temp
12:21:37,936 INFO [Http11Protocol] Pausing Coyote HTTP/1.1 on http-127.0.0.1-8080
12:21:37,937 INFO [AjpProtocol] Pausing Coyote AJP/1.3 on ajp-127.0.0.1-8009
12:21:38,937 INFO [StandardService] Stopping service jboss.web
12:21:38,977 INFO [Http11Protocol] Stopping Coyote HTTP/1.1 on http-127.0.0.1-8080
12:21:38,978 INFO [AjpProtocol] Stopping Coyote AJP/1.3 on ajp-127.0.0.1-8009
12:21:38,981 INFO [TomcatDeployer] undeploy, ctxPath=/invoker, warUrl=.../deploy/http-invoker.sar/invoker.war/
12:21:38,982 INFO [TomcatDeployer] undeploy, ctxPath=/jbossws-context, warUrl=.../deploy/jbossws.sar/jbossws-context.war/
12:21:38,984 INFO [TomcatDeployer] undeploy, ctxPath=/jbossmq-httpil, warUrl=.../deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/
12:21:38,985 INFO [TomcatDeployer] undeploy, ctxPath=/web-console, warUrl=.../deploy/management/console-mgr.sar/web-console.war/
12:21:38,986 INFO [TomcatDeployer] undeploy, ctxPath=/jmx-console, warUrl=.../deploy/jmx-console.war/
And port 8080 is no longer open
[ejort at warjort deploy]$ netstat -an | grep 8080
[ejort at warjort deploy]$
Showing JBoss is doing it explictly/correctly.
If the port is still open then the underlying OS must have a reason for not closing
immediately when JBoss requests it or terminates.
> when the shutdown of the server is complete, some ports still been used (timing issue)
> --------------------------------------------------------------------------------------
>
> Key: JBAS-5468
> URL: http://jira.jboss.com/jira/browse/JBAS-5468
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Environment: Red Hat Application Stack V.1.3
> Reporter: Jehudi Castro
> Priority: Minor
>
> After the shutdown got the confirmation:
> 11:11:08,795 INFO [Server] Shutdown complete
> Shutdown complete
> Halting VM
> Then try to start the server again:
> [root at dhcp78-191 ~]# service jbossas start
> Starting jbossas: [FAILED]
> Port 8080 is busy, is there a Tomcat running?
> after a few seconds works fine
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list