This content has been marked as final.
Show 3 replies
-
1. Re: I have no clue why port is not listening **URGENT PLEASE
genman May 18, 2007 12:07 AM (in response to ninis_2)How is the server being started? There is a -b option to run.sh. Check "netstat" on the machine...
-
2. Re: I have no clue why port is not listening **URGENT PLEASE
ninis_2 May 18, 2007 8:04 AM (in response to ninis_2)There are some wraper scripts around the run.sh to start the server. The server logs say
/jboss/server/default/log> grep 10.8.8.28 *
server.log:2007-05-18 07:42:15,542 INFO [org.apache.coyote.http11.Http11BaseProtocol] Initializing Coyote HTTP/1.1 on http-10.8.8.28-8080
server.log:2007-05-18 07:44:48,302 INFO [org.apache.coyote.http11.Http11BaseProtocol] Starting Coyote HTTP/1.1 on http-10.8.8.28-8080
server.log:2007-05-18 07:44:48,710 INFO [org.apache.jk.common.ChannelSocket] JK: ajp13 listening on /10.8.8.28:8009 -
3. Re: I have no clue why port is not listening **URGENT PLEASE
ninis_2 May 18, 2007 8:57 AM (in response to ninis_2)when i do a net stat i get the following. Should it be 10.8.8.28:8080 instead of 10.8.8.28.8080? With my limited knowledge I am not sure if this is correct.
$netstat -an | fgrep 8080 10.8.8.28.8080 *.* 0 0 49152 0 LISTEN Thanks,