Support Article

The JBOSS on production support is going down with the following

SA-37955

Summary



The JBOSS on production support is going down with an error.


ERROR MESSAGES


2017-05-14 00:45:32,389 [ p03fsp0l3540] [ STANDARD] [ ] [ ] (.instance.DefaultAddressPicker) INFO - [LOCAL] [b2184b2c7b46cdc38177380a96b8b518] [3.4.1] Prefer IPv4 stack is true.
2017-05-14 00:45:32,390 [ p03fsp0l3540] [ STANDARD] [ ] [ ] (.instance.DefaultAddressPicker) WARN - [LOCAL] [b2184b2c7b46cdc38177380a96b8b518] [3.4.1] Could not find a matching address to start with! Picking one of non-loopback addresses.
2017-05-14 00:45:32,398 [ p03fsp0l3540] [ STANDARD] [ ] [ ] (.instance.DefaultAddressPicker) INFO - [LOCAL] [b2184b2c7b46cdc38177380a96b8b518] [3.4.1] Picked Address[IP1]:5701, using socket ServerSocket[addr=/0.0.0.0,localport=5701], bind any local is true
.
.

2017-05-14 00:45:32,967 [ p03fsp0l3540] [ STANDARD] [ ] [ ] ( hazelcast.instance.Node) INFO - [IP2]:5701 [b2184b2c7b46cdc38177380a96b8b518] [3.4.1] Hazelcast Shutdown is completed in 11 ms.



Steps to Reproduce



Reboot JBOSS


Root Cause



During the server start up, some server instances chose IP addresses associated to a NIC that does not map the machine's hostname and causing the reported hazelcast start-up failure.


Resolution



Administrator can force Hazelcast to use one NIC over another by specifying "cluster/hazelcast/members" setting in the prconfig.xml file.

For example:
<env name="cluster/hazelcast/members" value="123.123.123.121,123.123.123.123" />
Also please note while restarting the servers bring up the other nodes after primary node is completely up.

Published May 14, 2017 - Updated June 27, 2017

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.