FYI, and perhaps unrelated to this topic: yesterday a patch went in that
will by default set system prop java.net.preferIPv4Stack on these
processes. Absent that the JVM seems to prefer IPv6 addresses, which is
fine but often isn't what people expect.
On 4/28/11 3:14 PM, denstar wrote:
On Wed, Apr 27, 2011 at 8:43 AM, Brian Stansberry wrote:
...
> The handling of configuration.setBindAddress() is clearly off, and the end
> result in the ProcessController (which is what the HostController is failing
> to connect to in your stack) is listening on InetAddress.getLocalHost().
>
> That might not be the issue, but it has an odd smell; the todo clearly needs
> to be cleaned up.
Thanks for the hint! If I get a chance, I'll try to suss out what's
going down, as I'm seeing this rather consistently.
:Denny
--
Brian Stansberry
Principal Software Engineer
JBoss by Red Hat