[JBoss JIRA] Closed: (JBREM-910) CLONE -Connector.stop() cannot find invoker MBean when bind address is 0.0.0.0 [JBREM-909]
by Ron Sigal (JIRA)
[ 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://jira.jboss.com/jira/browse/JBREM-910
> Project: JBoss Remoting
> …
[View More]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.atlassian.com/software/jira
[View Less]
17 years
[JBoss JIRA] Closed: (JBREM-912) Remove stacktrace when SSLSocketBuilder.createSSLSocketFactory() fails
by Ron Sigal (JIRA)
[ http://jira.jboss.com/jira/browse/JBREM-912?page=all ]
Ron Sigal closed JBREM-912.
---------------------------
Resolution: Done
> Remove stacktrace when SSLSocketBuilder.createSSLSocketFactory() fails
> ----------------------------------------------------------------------
>
> Key: JBREM-912
> URL: http://jira.jboss.com/jira/browse/JBREM-912
> Project: JBoss Remoting
> Issue Type: Task
> Security Level: …
[View More]Public(Everyone can see)
> Affects Versions: 2.2.0.SP4
> Reporter: Ron Sigal
> Assigned To: Ron Sigal
> Priority: Minor
> Fix For: 2.2.2.SP7
>
>
> Remoting is too noisy in places when org.jboss.remoting.security.SSLSocketBuilder.createSSLSocketFactory() fails. In particular,
> org.jboss.remoting.transport.http.ssl.HTTPSClientInvoker.createSocketFactory()
> org.jboss.remoting.transport.sslbisocket.BisocketClientInvoker.createSocketFactory()
> org.jboss.remoting.transport.sslbisocket.BisocketServerInvoker.createSocketFactory()
> org.jboss.remoting.transport.bisocket.SocketClientInvoker.createSocketFactory()
> print stacktraces at ERROR log level. It would be better if they just printed a message at ERROR level and saved the stacktrace for DEBUG 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
[View Less]
17 years
[JBoss JIRA] Updated: (JBREM-912) Remove stacktrace when SSLSocketBuilder.createSSLSocketFactory() fails
by Ron Sigal (JIRA)
[ http://jira.jboss.com/jira/browse/JBREM-912?page=all ]
Ron Sigal updated JBREM-912:
----------------------------
Fix Version/s: 2.2.2.SP7
(was: 2.2.2.SP5)
> Remove stacktrace when SSLSocketBuilder.createSSLSocketFactory() fails
> ----------------------------------------------------------------------
>
> Key: JBREM-912
> URL: http://jira.jboss.com/jira/browse/JBREM-912
> Project: JBoss Remoting
> …
[View More] Issue Type: Task
> Security Level: Public(Everyone can see)
> Affects Versions: 2.2.0.SP4
> Reporter: Ron Sigal
> Assigned To: Ron Sigal
> Priority: Minor
> Fix For: 2.2.2.SP7
>
>
> Remoting is too noisy in places when org.jboss.remoting.security.SSLSocketBuilder.createSSLSocketFactory() fails. In particular,
> org.jboss.remoting.transport.http.ssl.HTTPSClientInvoker.createSocketFactory()
> org.jboss.remoting.transport.sslbisocket.BisocketClientInvoker.createSocketFactory()
> org.jboss.remoting.transport.sslbisocket.BisocketServerInvoker.createSocketFactory()
> org.jboss.remoting.transport.bisocket.SocketClientInvoker.createSocketFactory()
> print stacktraces at ERROR log level. It would be better if they just printed a message at ERROR level and saved the stacktrace for DEBUG 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
[View Less]
17 years
[JBoss JIRA] Updated: (JBREM-910) CLONE -Connector.stop() cannot find invoker MBean when bind address is 0.0.0.0 [JBREM-909]
by Ron Sigal (JIRA)
[ 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://jira.jboss.com/jira/browse/JBREM-910
> …
[View More] 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.atlassian.com/software/jira
[View Less]
17 years
[JBoss JIRA] Reopened: (JBREM-910) CLONE -Connector.stop() cannot find invoker MBean when bind address is 0.0.0.0 [JBREM-909]
by Ron Sigal (JIRA)
[ 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://jira.jboss.com/jira/browse/JBREM-910
> Project: JBoss Remoting
> Issue …
[View More]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.atlassian.com/software/jira
[View Less]
17 years