Created: (JBREM-910) CLONE -Connector.stop() cannot find invoker MBean whe

Thread: Created: (JBREM-910) CLONE -Connector.stop() cannot find invoker MBean whe

Search this list only Search all lists
Created: (JBREM-910) CLONE -Connector.stop() cannot find invoker MBean whe
United States	2008-02-20 20:08:42
CLONE -Connector.stop() cannot find invoker MBean when bind address is 0.0.0.0 [JBREM-909] ------------------------------------------------------------ ------------------------------ Key: JBREM-910 URL: http://ji ra.jboss.com/jira/browse/JBREM-910 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Ron Sigal Assigned To: Ron Sigal Priority: Minor Fix For: 2.4.0.CR1 (Pinto) org.jboss.remoting.transport.Connector.init() registers its org.jboss.remoting.ServerInvoker with the MBeanServer using the ObjectName returned by ServerInvoker.getMBeanObjectName(), and Connector.stop() unregisters the same ServerInvoker using the ObjectName returned by ServerInvoker.getMBeanObjectName(). The problem is that Connector.init() calls ServerInvoker.getMBeanObjectName() before it calls ServerInvoker.create(), at which time ServerInvoker transforms the original 0.0.0.0 bind address into an actual address. Since the bind address is used in the ObjectName, the opening and closing calls to ServerInvoker.getMBeanObjectName() return different values when the original bind address is 0.0.0.0. -- 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.atl assian.com/software/jira _______________________________________________ jboss-jira mailing list jboss-jiralists.jboss.org h ttps://lists.jboss.org/mailman/listinfo/jboss-jira

Updated: (JBREM-910) CLONE -Connector.stop() cannot find invoker MBean whe
United States	2008-02-20 20:08:42
[ http://jira.jboss.com/jira/browse/JBREM-910?page=all ] Ron Sigal updated JBREM-910: ---------------------------- Fix Version/s: 2.2.2.SP5 (was: 2.4.0.CR1 (Pinto)) > CLONE -Connector.stop() cannot find invoker MBean when bind address is 0.0.0.0 [JBREM-909] > ------------------------------------------------------------ ------------------------------ > > Key: JBREM-910 > URL: http://ji ra.jboss.com/jira/browse/JBREM-910 > Project: JBoss Remoting > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Ron Sigal > Assigned To: Ron Sigal > Priority: Minor > Fix For: 2.2.2.SP5 > > > org.jboss.remoting.transport.Connector.init() registers its org.jboss.remoting.ServerInvoker with the MBeanServer using the ObjectName returned by ServerInvoker.getMBeanObjectName(), and Connector.stop() unregisters the same ServerInvoker using the ObjectName returned by ServerInvoker.getMBeanObjectName(). The problem is that Connector.init() calls ServerInvoker.getMBeanObjectName() before it calls ServerInvoker.create(), at which time ServerInvoker transforms the original 0.0.0.0 bind address into an actual address. Since the bind address is used in the ObjectName, the opening and closing calls to ServerInvoker.getMBeanObjectName() return different values when the original bind address is 0.0.0.0. -- 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.atl assian.com/software/jira _______________________________________________ jboss-jira mailing list jboss-jiralists.jboss.org h ttps://lists.jboss.org/mailman/listinfo/jboss-jira

Commented: (JBREM-910) CLONE -Connector.stop() cannot find invoker MBean w
United States	2008-02-25 20:36:42
[ http://jira.jboss.com/jira/browse/JBREM -910?page=comments#action_12400551 ] Ron Sigal commented on JBREM-910: --------------------------------- Now Connector.init() calls ServerInvoker.create() before calling ServerInvoker.getMBeanObjectName(). Unit test: org.jboss.test.remoting.transport.connector.ObjectNameWithZe roesAddressTestCase > CLONE -Connector.stop() cannot find invoker MBean when bind address is 0.0.0.0 [JBREM-909] > ------------------------------------------------------------ ------------------------------ > > Key: JBREM-910 > URL: http://ji ra.jboss.com/jira/browse/JBREM-910 > Project: JBoss Remoting > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Ron Sigal > Assigned To: Ron Sigal > Priority: Minor > Fix For: 2.2.2.SP5 > > > org.jboss.remoting.transport.Connector.init() registers its org.jboss.remoting.ServerInvoker with the MBeanServer using the ObjectName returned by ServerInvoker.getMBeanObjectName(), and Connector.stop() unregisters the same ServerInvoker using the ObjectName returned by ServerInvoker.getMBeanObjectName(). The problem is that Connector.init() calls ServerInvoker.getMBeanObjectName() before it calls ServerInvoker.create(), at which time ServerInvoker transforms the original 0.0.0.0 bind address into an actual address. Since the bind address is used in the ObjectName, the opening and closing calls to ServerInvoker.getMBeanObjectName() return different values when the original bind address is 0.0.0.0. -- 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.atl assian.com/software/jira _______________________________________________ jboss-jira mailing list jboss-jiralists.jboss.org h ttps://lists.jboss.org/mailman/listinfo/jboss-jira

Closed: (JBREM-910) CLONE -Connector.stop() cannot find invoker MBean when
United States	2008-02-26 00:13:44
[ http://jira.jboss.com/jira/browse/JBREM-910?page=all ] Ron Sigal closed JBREM-910. --------------------------- Resolution: Done Unit test passing locally. > CLONE -Connector.stop() cannot find invoker MBean when bind address is 0.0.0.0 [JBREM-909] > ------------------------------------------------------------ ------------------------------ > > Key: JBREM-910 > URL: http://ji ra.jboss.com/jira/browse/JBREM-910 > Project: JBoss Remoting > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Ron Sigal > Assigned To: Ron Sigal > Priority: Minor > Fix For: 2.2.2.SP5 > > > org.jboss.remoting.transport.Connector.init() registers its org.jboss.remoting.ServerInvoker with the MBeanServer using the ObjectName returned by ServerInvoker.getMBeanObjectName(), and Connector.stop() unregisters the same ServerInvoker using the ObjectName returned by ServerInvoker.getMBeanObjectName(). The problem is that Connector.init() calls ServerInvoker.getMBeanObjectName() before it calls ServerInvoker.create(), at which time ServerInvoker transforms the original 0.0.0.0 bind address into an actual address. Since the bind address is used in the ObjectName, the opening and closing calls to ServerInvoker.getMBeanObjectName() return different values when the original bind address is 0.0.0.0. -- 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.atl assian.com/software/jira _______________________________________________ jboss-jira mailing list jboss-jiralists.jboss.org h ttps://lists.jboss.org/mailman/listinfo/jboss-jira

Updated: (JBREM-910) CLONE -Connector.stop() cannot find invoker MBean whe
United States	2008-03-28 19:48:40
[ http://jira.jboss.com/jira/browse/JBREM-910?page=all ] Ron Sigal updated JBREM-910: ---------------------------- Fix Version/s: 2.2.2.SP7 (was: 2.2.2.SP5) > CLONE -Connector.stop() cannot find invoker MBean when bind address is 0.0.0.0 [JBREM-909] > ------------------------------------------------------------ ------------------------------ > > Key: JBREM-910 > URL: http://ji ra.jboss.com/jira/browse/JBREM-910 > Project: JBoss Remoting > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Ron Sigal > Assigned To: Ron Sigal > Priority: Minor > Fix For: 2.2.2.SP7 > > > org.jboss.remoting.transport.Connector.init() registers its org.jboss.remoting.ServerInvoker with the MBeanServer using the ObjectName returned by ServerInvoker.getMBeanObjectName(), and Connector.stop() unregisters the same ServerInvoker using the ObjectName returned by ServerInvoker.getMBeanObjectName(). The problem is that Connector.init() calls ServerInvoker.getMBeanObjectName() before it calls ServerInvoker.create(), at which time ServerInvoker transforms the original 0.0.0.0 bind address into an actual address. Since the bind address is used in the ObjectName, the opening and closing calls to ServerInvoker.getMBeanObjectName() return different values when the original bind address is 0.0.0.0. -- 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.atl assian.com/software/jira _______________________________________________ jboss-jira mailing list jboss-jiralists.jboss.org h ttps://lists.jboss.org/mailman/listinfo/jboss-jira

Reopened: (JBREM-910) CLONE -Connector.stop() cannot find invoker MBean wh
United States	2008-03-28 19:48:40
[ http://jira.jboss.com/jira/browse/JBREM-910?page=all ] Ron Sigal reopened JBREM-910: ----------------------------- > CLONE -Connector.stop() cannot find invoker MBean when bind address is 0.0.0.0 [JBREM-909] > ------------------------------------------------------------ ------------------------------ > > Key: JBREM-910 > URL: http://ji ra.jboss.com/jira/browse/JBREM-910 > Project: JBoss Remoting > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Ron Sigal > Assigned To: Ron Sigal > Priority: Minor > Fix For: 2.2.2.SP7 > > > org.jboss.remoting.transport.Connector.init() registers its org.jboss.remoting.ServerInvoker with the MBeanServer using the ObjectName returned by ServerInvoker.getMBeanObjectName(), and Connector.stop() unregisters the same ServerInvoker using the ObjectName returned by ServerInvoker.getMBeanObjectName(). The problem is that Connector.init() calls ServerInvoker.getMBeanObjectName() before it calls ServerInvoker.create(), at which time ServerInvoker transforms the original 0.0.0.0 bind address into an actual address. Since the bind address is used in the ObjectName, the opening and closing calls to ServerInvoker.getMBeanObjectName() return different values when the original bind address is 0.0.0.0. -- 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.atl assian.com/software/jira _______________________________________________ jboss-jira mailing list jboss-jiralists.jboss.org h ttps://lists.jboss.org/mailman/listinfo/jboss-jira

Closed: (JBREM-910) CLONE -Connector.stop() cannot find invoker MBean when
United States	2008-03-28 19:50:44
[ http://jira.jboss.com/jira/browse/JBREM-910?page=all ] Ron Sigal closed JBREM-910. --------------------------- Resolution: Done > CLONE -Connector.stop() cannot find invoker MBean when bind address is 0.0.0.0 [JBREM-909] > ------------------------------------------------------------ ------------------------------ > > Key: JBREM-910 > URL: http://ji ra.jboss.com/jira/browse/JBREM-910 > Project: JBoss Remoting > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Ron Sigal > Assigned To: Ron Sigal > Priority: Minor > Fix For: 2.2.2.SP7 > > > org.jboss.remoting.transport.Connector.init() registers its org.jboss.remoting.ServerInvoker with the MBeanServer using the ObjectName returned by ServerInvoker.getMBeanObjectName(), and Connector.stop() unregisters the same ServerInvoker using the ObjectName returned by ServerInvoker.getMBeanObjectName(). The problem is that Connector.init() calls ServerInvoker.getMBeanObjectName() before it calls ServerInvoker.create(), at which time ServerInvoker transforms the original 0.0.0.0 bind address into an actual address. Since the bind address is used in the ObjectName, the opening and closing calls to ServerInvoker.getMBeanObjectName() return different values when the original bind address is 0.0.0.0. -- 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.atl assian.com/software/jira _______________________________________________ jboss-jira mailing list jboss-jiralists.jboss.org h ttps://lists.jboss.org/mailman/listinfo/jboss-jira

[1-7]

about | contact Other archives ( Real Estate discussion Medical topics )