-
1. Re: Bound to localhost instead of VIP
xmedeko Jul 22, 2009 8:37 AM (in response to aiesulauro)The port 35876 does not seem to be some port allocated for any service. It might just something temporary. Is this port open aven after a while?
"aiesulauro" wrote:
Is this a problem? Is there any way to determine which JBoss deployment is listening on the port?
Under linux you can see commandline arguments of the running process, e.g. byps -ef | grep 13450
where 13450 is PID of the process. -
2. Re: Bound to localhost instead of VIP
aiesulauro Jul 22, 2009 10:20 AM (in response to aiesulauro)Thank you for your reply.
The port allocation seems to be permanent. The appServer instance has been up for 17 days and port 35876 is still open.
The JVM command line arguments follow./usr2/jboss/jdk1.6.0_06/bin/java -Dprogram.name=run.sh -server -Xms128m -Xmx512m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.net.preferIPv4Stack=true -Djava.endorsed.dirs=/usr2/jboss/jboss-5.1.0.GA/lib/endorsed -classpath /usr2/jboss/jboss-5.1.0.GA/bin/run.jar /usr2/jboss/jdk1.6.0_06/lib/tools.jar org.jboss.Main -b jestdev03 -Pboot.properties
Tony -
3. Re: Bound to localhost instead of VIP
xmedeko Jul 24, 2009 4:36 AM (in response to aiesulauro)I do not see any -c parameter from the command line arguments you have posted. And I see some unusual "-Pboot.properties" parameter. So I guess you start your JBoss in some unusual way. What's inside boot.properties?
I have searched my JBoss installation for the 35876 string, but cannot find anything relevant.
I have something like "-c default" -
4. Re: Bound to localhost instead of VIP
aiesulauro Jul 24, 2009 10:06 AM (in response to aiesulauro)The boot.properties file is used to set several system properties. One system property being set is jboss.server.name, the name of the server configuration. This property corresponds to the value of the minus c option to the run script. The contents of the boot.properties file is shown in the code block below.
My guess is that the port number is assigned dynamically because when I cycle the appServer a different port is assigned each time it initializes. And other JBoss510 appServer instances on the same host have different port numbers bound to localhost.localdomain.jboss.home.dir=/usr2/jboss/jboss-5.1.0.GA jboss.java.home.dir=/usr2/jboss/jdk1.6.0_06 jboss.lib.url=file:/usr2/jboss/jboss-5.1.0.GA/lib jboss.home.url=file:/usr2/jboss/jboss-5.1.0.GA jboss.server.name=default jboss.server.base.dir=/jboss/deploy/JBOSS510/JB510.1.0/server/ jboss.server.base.url=file:/jboss/deploy/JBOSS510/JB510.1.0/server/ jboss.server.home.dir=/jboss/deploy/JBOSS510/JB510.1.0/server/default jboss.server.home.url=file:/jboss/deploy/JBOSS510/JB510.1.0/server/default