]
Bela Ban commented on JGRP-1280:
--------------------------------
The solution is to create another annotation @LocalAddress, and check that every bind
address annotated with @LocalAddress is a valid address on a local network interface.
Fixed on 2.12, backported to 2.11.2 as well.
Bind error messages should report incorrect IP addresses
--------------------------------------------------------
Key: JGRP-1280
URL:
https://issues.jboss.org/browse/JGRP-1280
Project: JGroups
Issue Type: Enhancement
Affects Versions: 2.11
Reporter: Manik Surtani
Assignee: Bela Ban
Labels: exceptions
Fix For: 2.11.2, 2.12
Not tried on 2.12, etc as yet. This is when you specify an incorrect bind address - one
that is not available on the target host - and instead of reporting this, JGroups attempts
to increase the port number and retry, eventually failing with a port being out of range.
This can be very misleading as it leads you to debug conflicting ports, etc., when in fact
the problem is a badly configured IP address.
This was reported a few years back on the forums, but I've still seen the issue on
JGroups 2.11.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: