-
1. Re: Cannot connect to JBoss instance using FQDN
wdfink Jan 13, 2012 2:40 AM (in response to sbass)How do you start the JBoss and what version it is?
I suppose you start without option "-b x.x.x.x", in this case current JBoss versions only bind against the 127.0.0.1 interface.
Try -b 0.0.0.0 to bind against all, or -b <your IP> to bind against your IP address.
If you have still used -b you may have a firewall in between
-
2. Re: Cannot connect to JBoss instance using FQDN
sbass Jan 13, 2012 7:05 PM (in response to wdfink)Hi,
Summary: -b 0.0.0.0 fixed the problem.
Details: We're experiencing stability and out-of-memory errors with our 4.2.2 JBoss web applications. The vendor (SAS) recommended upgrading from JDK 5/JBoss 4.2.0 to JDK 6/JBoss 4.2.3. Another vendor (Futrix) suggested splitting out the SAS & Futrix web applications into their own server instances (currently all web apps are in the one JBoss server instance)
The old instances run as a service using wrapper.exe and wrapper.conf. I was running the new instance from run.bat while I work out the kinks in the software migration. I'll install them as a service as a final step.
I'd missed the -b 0.0.0.0 parameter from wrapper.conf when I started the new instances using run.bat. Adding -b to the run.bat command line caused the new instances to listen on both localhost and machinename.
Thanks for the help. Much appreciated.
Scott