Uploaded image for project: 'JBoss Remoting'
  1. JBoss Remoting
  2. JBREM-747

org.jboss.remoting.transport.Connector should unregister server invoker from MBeanServer

    XMLWordPrintable

    Details

      Description

      The JBossMessaging secure-socket smoke test uncovered the fact that Connector does not unregister its server invoker from the MBeanServer (if it has a reference to one).

      The problem detected by the JBossMessaging was that when secure-socket runs twice, the first execution passes and the second fails with the exception

      javax.net.ssl.SSLException: No available certificate or key corresponds to the SSL cipher suites which are enabled.
      at com.sun.net.ssl.internal.ssl.SSLServerSocketImpl.checkEnabledSuites(SSLServerSocketImpl.java:303)
      at com.sun.net.ssl.internal.ssl.SSLServerSocketImpl.accept(SSLServerSocketImpl.java:253)
      at org.jboss.remoting.transport.bisocket.BisocketServerInvoker$SecondaryServerSocketThread.run(BisocketServerInvoker.java:799)

      The problem was that at the end of the first execution, Connector failed to unregister the server invoker, and during the second execution, it saw the ObjectName registered. The Connector.init() code then failed to pass a reference to the MBeanServer to the server invoker. As a result the server invoker was unable to access the SSLServerSocketFactory MBean configured by the test, and it used a default server socket factory instead.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  ron_sigal Ron Sigal
                  Reporter:
                  ron_sigal Ron Sigal
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  0 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: