I remembered i have run it while the previous one was still running. Then i killed the process id used in running JBOSS(not a graceful way to shutdown), and i think that left the ports open. So maybe my problem is how to manually close the ports?
Doing either a CTRL-C or killing the process (except for maybe a "kill -9") will cause JBoss AS to shut down gracefully, which includes closing the ports. For 'kill -9' the OS should be reclaiming the ports.
Run a netstat to determine which ports JBoss AS is using. See: http://community.jboss.org/wiki/DebugBindException Also, when using shutdown, pass the JNDI port, not the HTTP port (you post is unclear as to whether JNDI or HTTP is using port 38080).
Thanks for your reply. It has been quite awhile, and by now the problem has gone away, but i didn't resolved it, and i wanted to clarify on the would-have-been a solution to the problem i had.
Yes, 38080 was HTTP port number instead of JNDI.
But which one are you exactly referring to for JNDI?
Referring back to my server-bindings.xml as below, is it under my Naming config, and if so, then in the example below, do i take the RmiPort 31098 or binding port 31099?
Instead of $PKG_NAME use uatappl001.opticx.com and this will work !!
So the final command should be
$JBOSS_HOME/bin/shutdown.sh -s jnp://uatappl001.opticx.com:31099
Vikram
SCJP 5 , SCBCD [Prep Started ] , WLS 8.1 Server Admin
Jonilie Echavez
Greenhorn
Joined: Jun 26, 2009
Posts: 20
posted
0
Thank you all! Your comments were helpful and it worked!