Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-10990

Legacy EJB client dependency in wildfly-feature-pack breaks AS TS

XMLWordPrintable

    • Blocks Testing
    • Hide 
      git clone -b JBEAP-10990-reproducer https://github.com/kwart/wildfly.git
cd wildfly
mvn clean install -DskipTests
cd testsuite/integration/elytron
mvn clean test -Dtest=DefaultSaslConfigTestCase

      You can also look into this Build Log:
      https://ci.wildfly.org/viewLog.html?buildId=59900&buildTypeId=WFPR&tab=buildLog

      Show
      git clone -b JBEAP-10990-reproducer https: //github.com/kwart/wildfly.git cd wildfly mvn clean install -DskipTests cd testsuite/integration/elytron mvn clean test -Dtest=DefaultSaslConfigTestCase You can also look into this Build Log: https://ci.wildfly.org/viewLog.html?buildId=59900&buildTypeId=WFPR&tab=buildLog

      The new jboss-ejb-client-legacy dependency in wildfly-feature-pack POM breaks AS TS client tests. Users can hit this issue too if they define dependencies using the feature-pack pom.

              <dependency>
            <groupId>org.wildfly</groupId>
            <artifactId>wildfly-feature-pack</artifactId>
            <type>pom</type>
        </dependency>

      The AS testsuite/shared module has a dependency on wildfly-feature-pack POM which newly introduces the legacy EJB client dependency. (https://github.com/wildfly/wildfly/pull/10061/files) It results in classpath issues.

      When I hit the issue in my test, the test prints just this exception and the testsuite run hangs forever:

      Exception in thread "XNIO-1 task-14" java.lang.NoSuchMethodError: org.jboss.ejb.client.Affinity.forUri(Ljava/net/URI;)Lorg/jboss/ejb/client/Affinity;
	at org.jboss.ejb.protocol.remote.ProtocolV3ObjectResolver.<init>(ProtocolV3ObjectResolver.java:43)
	at org.jboss.ejb.protocol.remote.EJBMarshallingCompatibilityHelper.getObjectResolver(EJBMarshallingCompatibilityHelper.java:42)
	at org.wildfly.naming.client.remote.RemoteClientTransport$1.handleMessage(RemoteClientTransport.java:155)
	at org.jboss.remoting3.remote.RemoteConnectionChannel.lambda$handleMessageData$3(RemoteConnectionChannel.java:434)
	at org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:897)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:748)

              kkhan1@redhat.com Kabir Khan
              josef.cacek@gmail.com Josef Cacek (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: