Bind JBoss EAP to 0.0.0.0 and allow remote connectivity when no DNS is available
Issue
- Our servers must bind to
0.0.0.0because of legacy application requirements. For some reason remote EJB3 and JMS clients cannot connect. We suspect it is because we have no DNS in our environment. - When I bind my JBoss instance to
0.0.0.0, RMI clients cannot connect, but if I bind to a specific IP address, the clients can connect. Why is this?
Environment
- Red Hat JBoss Enterprise Application Platform (EAP)
- 4.3
- 5.x
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.
