Project and Portfolio Management Practitioners Forum
cancel
Showing results for 
Search instead for 
Did you mean: 

Adding new nodes on 6.0, SP17 installation - binding error

Highlighted
Alan Delimon
Regular Collector

Adding new nodes on 6.0, SP17 installation - binding error

We added a few new JBoss nodes to $ITG_HOME/server. When we start them up, they get the following error on a 6.0, SP17 installation on Solaris:
jboss.web:service=WebServer JBossWeb:main:org.jboss.jetty.JettyService:2008/06/10-16:38:41.412 EDT: multiple exceptions...
jboss.web:service=WebServer JBossWeb:main:org.jboss.jetty.JettyService:2008/06/10-16:38:41.419 EDT: exception
java.net.BindException: Address already in use

However, they are configured properly in server.conf, and should not be binding to any ports by nodes already started up.

This is an example of a working nodes:
@node
com.kintana.core.server.KINTANA_SERVER_NAME=ISIntegrity4
com.kintana.core.server.RMI_URL=rmi://kntatst-app.paetec.com:1102/KintanaServer
com.kintana.core.server.EXTERNAL_WEB_PORT=8086
com.kintana.core.server.HTTP_PORT=8088
com.kintana.core.server.TURN_ON_WF_TIMEOUT_REAPER=TRUE

And this is an example of one that has the exception:
@node
com.kintana.core.server.KINTANA_SERVER_NAME=ISIntegrity5
com.kintana.core.server.RMI_URL=rmi://kntatst-app.paetec.com:1103/KintanaServer
com.kintana.core.server.EXTERNAL_WEB_PORT=8089
com.kintana.core.server.HTTP_PORT=8091

As you can see, they are binding to different ports.

In this example, ISIntegrity5 was created by copying from ISIntegrity4. The servers were created by following the documentation.

KStatus reports that the server is up, and lsof reports that it is listening on the RMI port.

We are seeking help with this as it is currently going on on our production server.

HP Support has told us that it is the HTTP port, and suggested that something may already be bound there. But LSOF tells me otherwise. Anyone had this issue before?
bash-3.00$ /opt/satools/shared/lsof_10/lsof | grep LISTEN | grep :80
java 12177 chainlink 9u IPv4 0x6000c9f3280 0t0 TCP *:8083 (LISTEN)
java 12177 chainlink 11u IPv4 0x30000835080 0t0 TCP *:8081 (LISTEN)
java 12704 chainlink 9u IPv4 0x60009815180 0t0 TCP *:8084 (LISTEN)
java 12704 chainlink 11u IPv4 0x6000c4b0c80 0t0 TCP *:8082 (LISTEN)
java 12918 chainlink 9u IPv4 0x60016962180 0t0 TCP *:8087 (LISTEN)
java 12918 chainlink 11u IPv4 0x6000c4ee100 0t0 TCP *:8085 (LISTEN)
java 13139 chainlink 9u IPv4 0x6000c5434c0 0t0 TCP *:8088 (LISTEN)

As you can see nothing is bound, for reference, here is the list of http ports in server.conf:
com.kintana.core.server.HTTP_PORT=8083
com.kintana.core.server.HTTP_PORT=8084
com.kintana.core.server.HTTP_PORT=8087
com.kintana.core.server.HTTP_PORT=8088
com.kintana.core.server.HTTP_PORT=8091
com.kintana.core.server.HTTP_PORT=8092
com.kintana.core.server.HTTP_PORT=8095
com.kintana.core.server.HTTP_PORT=8098
2 REPLIES
Jim Esler
Honored Contributor

Re: Adding new nodes on 6.0, SP17 installation - binding error

You are only checking for LISTEN ports. The port may be open for other uses. grep for all TCP ports.
Alan Delimon
Regular Collector

Re: Adding new nodes on 6.0, SP17 installation - binding error

Something odd was going on with our kUpdateHTML script. We ran this again, and it worked perfectly. Our production system has been humming along flawlessly on 8 JVMs since.
//Add this to "OnDomLoad" event