Uploaded image for project: 'Remoting JMX'
  1. Remoting JMX
  2. REMJMX-36

The SecurityClientTest currently contains a static reference to the config - this means that depending on the order the tests are executed the wrong config could be used.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 1.0.3.CR1
    • 1.0.2.Final
    • Tests
    • None

      An example failure caused by the differing orders is: -

      -------------------------------------------------------------------------------
      Test set: org.jboss.remotingjmx.SecurityClientTest
      -------------------------------------------------------------------------------
      Tests run: 4, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 1.984 sec <<< FAILURE!
      testAnonymousAuthentication(org.jboss.remotingjmx.SecurityClientTest) Time elapsed: 0.116 sec <<< ERROR!
      javax.security.sasl.SaslException: Cannot get userid/password [Caused by javax.security.auth.callback.UnsupportedCallbackException]
      at com.sun.security.sasl.ClientFactoryImpl.getUserInfo(ClientFactoryImpl.java:157)
      at com.sun.security.sasl.ClientFactoryImpl.createSaslClient(ClientFactoryImpl.java:94)
      at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities$1.run(ClientConnectionOpenListener.java:352)

              darran.lofthouse@redhat.com Darran Lofthouse
              darran.lofthouse@redhat.com Darran Lofthouse
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: