[ http://jira.jboss.com/jira/browse/JBAS-4704?page=comments#action_12377568 ] Carlo de Wolf commented on JBAS-4704: ------------------------------------- Wrong assessment: in InvokerLocator there is a check on 0.0.0.0 which is then replaced by InetAddress.getLocalHost(). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBAS-4704?page=all ] Dimitris Andreadis updated JBAS-4704: ------------------------------------- Priority: Major (was: Blocker) User should not define the severity level. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBAS-4704?page=comments#action_12377622 ] Dimitris Andreadis commented on JBAS-4704: ------------------------------------------ The severity is set by the developer after assement of an issue. In production environments, wouldn't the most common usecase be to bind to a specify NIC and not all? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBAS-4704?page=comments#action_12377714 ] Ron Sigal commented on JBAS-4704: --------------------------------- There are two related issues in Remoting: 1) JBREM-687 "allow binding to 0.0.0.0": Prior to JBREM-687, Remoting would translate 0.0.0.0 to either InetAddress.getLocalHost().getHostName() or InetAddress.getLocalHost().getHostAddress() to generate (1) a bind address and (2) an address in the InvokerLocator (that is, the pointer used by the client to find the server). The fix for JBREM-687 causes Remoting to use 0.0.0.0 as the bind address and then translate 0.0.0.0 to either the local host name or address for use in the InvokerLocator. This issue is closed, with the fix applied to the branch which will yield Remoting 2.4.0. 2) JBREM-643 "configuration for multi-homed server invokers". This issue is still open and scheduled for Remoting 2.4. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBAS-4704?page=comments#action_12379301 ] Ron Sigal commented on JBAS-4704: --------------------------------- Dimitris, JBREM-607 "Add idle timeout setting for invoker threads" can't be what you mean. Can you check again? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBAS-4704?page=comments#action_12380853 ] Ron Sigal commented on JBAS-4704: --------------------------------- I've created a new release, 2.2.2.SP2, targeted for the next release of community AS 4.2.x (which looks like 4.2.3) and I've reopened JBREM-687 and added 2.2.2.SP2 as a fix version. Two questions: 1) What is the time frame for the release of AS 4.2.3, and 2) Does anyone know if this problem has ever appeared in a support case? If so, I'll target the fix for a CP release as well. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBAS-4704?page=comments#action_12381062 ] Ron Sigal commented on JBAS-4704: --------------------------------- -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBAS-4704?page=comments#action_12382381 ] Dimitris Andreadis commented on JBAS-4704: ------------------------------------------ http://repository.jboss.com/jboss/remoting/2.2.2.SP2/lib/ -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBAS-4704?page=com.atlassian.jira.plug... ] Ron Sigal closed JBAS-4704. --------------------------- Resolution: Done I'm closing this issue, since I believe it is solved as of Remoting version 2.2.2 SP2. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBAS-4704?page=com.atlassian.jira.plug... ] Ron Sigal closed JBAS-4704. --------------------------- Fix Version/s: JBossAS-4.2.4.GA Resolution: Done Associating a fix version so it gets recorded for posterity. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira