Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-6303

RemotingLoginModuleTestCase fails with the latest IBM jdk 20160108_01(SR2 FP10)

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Minor
    • Resolution: Done
    • Affects Version/s: 10.0.0.Final
    • Fix Version/s: 10.1.0.CR1, 10.1.0.Final
    • Component/s: Test Suite
    • Labels:
      None
    • Environment:

      Description

      org.jboss.as.test.integration.security.loginmodules.RemotingLoginModuleTestCase starts failing with the latest IBM jdk.

      ./integration-tests.sh clean test -Dmaven.repo.local=$REPO -Dts.noSmoke -Dts.basic -Dtest=RemotingLoginModuleTestCase
      Running org.jboss.as.test.integration.security.loginmodules.RemotingLoginModuleTestCase
      Tests run: 3, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.546 sec <<< FAILURE! - in org.jboss.as.test.integration.security.loginmodules.RemotingLoginModuleTestCase
      testNotAuthorizedClient(org.jboss.as.test.integration.security.loginmodules.RemotingLoginModuleTestCase)  Time elapsed: 0.031 sec  <<< ERROR!
      javax.naming.CommunicationException: Failed to connect to any server. Servers tried: [remote://127.0.0.1:14447 (javax.net.ssl.SSLException: Received fatal alert: handshake_failure)]
              at org.jboss.naming.remote.client.HaRemoteNamingStore.failOverSequence(HaRemoteNamingStore.java:244)
              at org.jboss.naming.remote.client.HaRemoteNamingStore.namingStore(HaRemoteNamingStore.java:149)
              at org.jboss.naming.remote.client.HaRemoteNamingStore.namingOperation(HaRemoteNamingStore.java:130)
              at org.jboss.naming.remote.client.HaRemoteNamingStore.lookup(HaRemoteNamingStore.java:272)
              at org.jboss.naming.remote.client.RemoteContext.lookupInternal(RemoteContext.java:104)
              at org.jboss.naming.remote.client.RemoteContext.lookup(RemoteContext.java:93)
              at org.jboss.naming.remote.client.RemoteContext.lookup(RemoteContext.java:146)
              at javax.naming.InitialContext.lookup(InitialContext.java:428)
              at org.jboss.as.test.integration.security.loginmodules.RemotingLoginModuleTestCase.testNotAuthorizedClient(RemotingLoginModuleTestCase.java:179)
       
      testAuthorizedClient(org.jboss.as.test.integration.security.loginmodules.RemotingLoginModuleTestCase)  Time elapsed: 0.026 sec  <<< ERROR!
      javax.naming.CommunicationException: Failed to connect to any server. Servers tried: [remote://127.0.0.1:14447 (javax.net.ssl.SSLException: Received fatal alert: handshake_failure)]
              at org.jboss.naming.remote.client.HaRemoteNamingStore.failOverSequence(HaRemoteNamingStore.java:244)
              at org.jboss.naming.remote.client.HaRemoteNamingStore.namingStore(HaRemoteNamingStore.java:149)
              at org.jboss.naming.remote.client.HaRemoteNamingStore.namingOperation(HaRemoteNamingStore.java:130)
              at org.jboss.naming.remote.client.HaRemoteNamingStore.lookup(HaRemoteNamingStore.java:272)
              at org.jboss.naming.remote.client.RemoteContext.lookupInternal(RemoteContext.java:104)
              at org.jboss.naming.remote.client.RemoteContext.lookup(RemoteContext.java:93)
              at org.jboss.naming.remote.client.RemoteContext.lookup(RemoteContext.java:146)
              at javax.naming.InitialContext.lookup(InitialContext.java:428)
              at org.jboss.as.test.integration.security.loginmodules.RemotingLoginModuleTestCase.testAuthorizedClient(RemotingLoginModuleTestCase.java:165)
      

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  mchoma Martin Choma
                  Reporter:
                  mchoma Martin Choma
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  2 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: