Process Automation binding to wrong IP address

Products

• CA Process Automation Base

Issue/Introduction

In environments where a server has two Network bindings, it may be observed that the server is taking the wrong server address - for instance, if there is a Primary and Secondary network card.

To see if this is occurring, look at the output of "netstat -a". The java.exe process will be listed with the IP address bound to the port for listening; by default on 8080 for HTTP, 8443 for HTTPS.

For example:

TCP    1.2.3.4:8080     0.0.0.0:0              LISTENING       12345

The above IP is (as per the output) bound to this port which is listening on process 12345, an example PID for the java application.

Environment

Release : 4.3.X

Component : Process Automation

Resolution

Process Automation will take the first listed network connection by default; usually the simplest solution here is to reverse their name order.

If this is not possible, then in PAM\server\c2o\bin\c2osvcw.conf you will find the line

wrapper.app.parameter.6=0.0.0.0

You can hardcode it there instead of 0.0.0.0 - this does make the configuration less portable, which is why it is recommended to change the bind order if possible. In addition, you can then add the following to the oasisconfig.properties to set the IP for JBOSS:

jboss.bind.address=mainIPaddress

so in the case of one server that's

jboss.bind.address=1.2.3.4

and then on the other

jboss.bind.address=1.2.3.5