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

Details

    • 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

    Description

      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)

      Attachments

        Issue Links

          is caused by

          Feature Request - Feature requests from customers and/or users JBEAP-10759 Add bom for legacy compatibility library, and tests to verify usage

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Verified

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-10859 Include org.jboss.eap:wildfly-ejb-client-legacy-bom and org.jboss:jboss-ejb-client-legacy in product Maven repo

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Verified
          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. WFLY-8801 Legacy EJB client dependency in wildfly-feature-pack breaks AS TS

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: