[
https://issues.jboss.org/browse/JGRP-1290?page=com.atlassian.jira.plugin....
]
Bela Ban commented on JGRP-1290:
--------------------------------
OK, I tried this on my Windows 7 system. JDK was 1.6.0-24. The problem was not
reproduceable, a BindException was thrown *not* a SocketException.
Obviously, this bug was fixed some time between build 18 and 24.
I'm not going to change code in JGroups, as the solution is to upgrade to a more
recent JDK on Windows 7
Windows 7 might throw SocketException instead of BindException
--------------------------------------------------------------
Key: JGRP-1290
URL:
https://issues.jboss.org/browse/JGRP-1290
Project: JGroups
Issue Type: Enhancement
Affects Versions: 2.12
Environment: Windows 7
Reporter: Manuel Dominguez Sarmiento
Assignee: Bela Ban
Priority: Minor
Fix For: 2.12.1
This is not actually a JGroups bug, it's more of a Sun JVM bug. See the following:
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6939037
In short, when a port is in use in Windows 7, SocketException is thrown instead of the
more specific BindException.
JGroups has code in several places that probes for available ports. Perhaps Windows 7
should be detected, and SocketException be caught instead of BindException in these
circumstances.
Before anyone cries out "get a real OS", we use RHEL on our production servers,
but some of our developers use Windows 7 on their development boxes.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira