[ https://jira.jboss.org/browse/JBAS-7930?page=com.atlassian.jira.plugin.sy... ] Brian Stansberry updated JBAS-7930: ----------------------------------- Fix Version/s: 7.0.0.M1 (was: 6.0.0.M4) Note that this won't work for FD_SOCK, as multiple FD_SOCK instances may use the same config; JGroups needs freedom to find an available port. Having FD_SOCK be a named singleton a la the transport protocols would solve thiis problem. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBAS-7930?page=com.atlassian.jira.plugin.... ] Jason Greene reopened JBAS-7930: -------------------------------- Due to feedback from the community, I have split the AS7 and AS6 projects and reopened all unscheduled AS6 issues that are a year or less old. This will make it easier community members to find and work on them. Future releases beyond 6.1 can be done provided a community member steps up to coordinate them. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-1254?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-1254: ---------------------------------- Assignee: (was: Brian Stansberry) Fix Version/s: 7.1.0.Beta2 Description: Lock down the ports. (was: Lock down the ports. Do this for M4 as it may lead to testsuite troubles on slaves until we identify ports where there aren't conflicts.) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-1254?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-1254: ---------------------------------- Assignee: Paul Ferraro Assigning to Paul, since if it is not valid any longer, Paul would know best. If it's not valid it's because JGroups' default behavior has changed, which I doubt. The issue is JGroups when it opens sockets will start at the configured port number and if it is not available will start incrementing the port looking for an available port. The port_range config can control how far it increments looking for a port. Setting the default port_range to 1 is another way of saying, "By default, use the socket configs the admin specified or fail; don't open sockets on unexpected ports." -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-1254?page=com.atlassian.jira.plugin.s... ] Jason Greene updated AS7-1254: ------------------------------ Fix Version/s: 7.1.0.CR1 (was: 7.1.0.Beta1) Moving all non-critical issues to the CR. If you finish it before we release beta please correct the fix-for version. Thanks -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-1254?page=com.atlassian.jira.plugin.s... ] Jason Greene updated AS7-1254: ------------------------------ Priority: Blocker (was: Major) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira