A JGroups bind address 127.0.0.1 might be useless as server messages from other boxes are not received, so the cluster will be affected.
If you use a public address and have other instances they should find each other.
Other subsystems might be able to use the 0.0.0.0 address to bind against every NIC.
The jgroups.bind_addr does not affect your public server address
First of, thanks for responding!
Thing is I'm not running Wildfly in a cluster of any sort.
I'm running a singe standalone instance.
Understand that if I remove the @Cacheable annotation from all entities in the JPA project the problem goes away immediately.
Also, if i set the public interface IP address in standalone.xml to 127.0.0.1 the problem also goes away!
The challenge is if I leave the public interface at 127.0.0.1 then all external web service clients cannot access the webservices on the application.
On the other hand, if I change the public interface to 0.0.0.0 then jgroups give an "invalid interface 0.0.0.0" exception on start up and the application doesn't get deployed.
Based on this explanation, what's your recommendation???
Could you use the public IP address? 0.0.0.0 mean all interfaces and will not work for JGroups.
But if you don't use a cluster, you might start a profile without clustering (standalone or standalone-full) in this case no JGroups subsysem is used.
You were right! Problem goes away the minute I used the actual public IP of the server.