Architecting, installing and maintaining your SAS environment

Problems with multiple instances from JBoss: Error starting ServerSocket. Bind port: 4446

Reply
SAS Employee
Posts: 10

Problems with multiple instances from JBoss: Error starting ServerSocket. Bind port: 4446

Hi there,

we have problems with starting the JBoss . We have on one Linux Machine two SAS environments (test and production) with own metadata and two JBoss instances. The both JBoss instances aren’t clustered, they are running independently from each other’s (SASServer<n>.sh) . We can start the first JBoss instance without errors. If we start the second JBoss instance we get the error message in the stdout.log from SASServer2:

13:49:08,073 ERROR [SocketServerInvoker] Error starting ServerSocket.  Bind port: 4446, bind address: /0.0.0.0

13:49:08,073 ERROR [Connector] Error starting connector.

java.net.BindException: Address already in use

13:49:08,796 ERROR [SocketServerInvoker] Error starting ServerSocket.  Bind port: 3873, bind address: /0.0.0.0

13:49:08,796 ERROR [Connector] Error starting connector.

java.net.BindException: Address already in use

OK, we have to change the port 4446 and 3873  - I think only by editing the file jboss.port.bindings.xml.
On which port shall we change the second instance of JBoss? 14446 or 4546 or what?
And, is it sufficient to edit the file jboss.port.bindings.xml or do we need more customizing?

Thanks in advance for informations and support

Brigitte

Attachment
PROC Star
Posts: 392

Problems with multiple instances from JBoss: Error starting ServerSocket. Bind port: 4446

Hi Brigitte,

Have you seen the the JBoss ports document in the support.sas.com Third-Party Software Reference section and the JBoss community wiki page it also references:

The SAS doc provides instructions on switching between the ports-01, ports-02, ports-03 port banks.  This avoids having to manually choose each port (since there are many of them). As long as each JBoss instance is using a different port bank they won't conflict.  There is more info in the referenced JBoss wiki page too.  I have successfully used this method to run 3 independant JBoss instances on the one machine.

I hope this helps you resolve the issue.

Cheers

Paul

SAS Employee
Posts: 10

Problems with multiple instances from JBoss: Error starting ServerSocket. Bind port: 4446

Hi Paul,

thank you very much for your support!

The entries in the file sample-bindings.xml assist us by editing the ports-02. Also we deleted the contents of the directories tmp and work under JBOSS_HOME/server/default/ and restarted the remote Services and JBoss. Now we have no error messages anymore :-).

Best regards,

Brigitte

Ask a Question
Discussion stats
  • 2 replies
  • 2482 views
  • 4 likes
  • 2 in conversation