[
https://issues.jboss.org/browse/JGRP-1290?page=com.atlassian.jira.plugin....
]
Manuel Dominguez Sarmiento commented on JGRP-1290:
--------------------------------------------------
AFAIK, just Windows 7. Windows XP works fine, throwing BindException. Don't know about
Windows Vista.
It would seem this just happens with Windows 7, as Googling for
"java.net.SocketException: Unrecognized Windows Sockets error: 0: JVM_Bind"
seems to bring bug reports and complaints from Windows 7 users only.
It also seems this happens with both 32-bit and 64-bit Windows 7 builds.
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
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