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

[GSS](7.4.z) WFLY-17209 - jboss-client.jar is missing jboss-modules classes which are required by jboss-ejb-client

    XMLWordPrintable

Details

    • Bug
    • Resolution: Won't Do
    • Major
    • None
    • 7.4.7.GA
    • Build System, EJB
    • False
    • None
    • False
    • Hide
      Reverted upstream https://github.com/wildfly/wildfly/pull/16230. The customer's problem will be resolved with JBEAP-24148.
      Show
      Reverted upstream https://github.com/wildfly/wildfly/pull/16230 . The customer's problem will be resolved with JBEAP-24148 .
    • Hide

      1) Deploy JBEAP-24130.jar in $JBOSS_HOME/standalone/deployments/

      2) Add user:

      $JBOSS_HOME/bin/add-user.sh -a -u ejbuser -p redhat1!

      3) Start EAP ./bin/standalone.sh

      4) Run the test client:
      java -cp $JBOSS_HOME/bin/client/jboss-client.jar:$JBOSS_HOME/standalone/deployments/JBEAP-24130.jar com.jboss.examples.ejb.HelloClient
      In Update 6, the ejb is invoked successfully

      In Update 7, the client fails with a ClassNotFound

      Show
      1) Deploy JBEAP-24130 .jar in $JBOSS_HOME/standalone/deployments/ 2) Add user: $JBOSS_HOME/bin/add-user.sh -a -u ejbuser -p redhat1! 3) Start EAP ./bin/standalone.sh 4) Run the test client: java -cp $JBOSS_HOME/bin/client/jboss-client.jar:$JBOSS_HOME/standalone/deployments/ JBEAP-24130 .jar com.jboss.examples.ejb.HelloClient In Update 6, the ejb is invoked successfully In Update 7, the client fails with a ClassNotFound

    Description

      jboss-client.jar is missing jboss-modules classes which are required by jboss-ejb-client

      Attachments

        Issue Links

          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. WFLY-17209 jboss-client.jar is missing jboss-modules classes which are required by jboss-ejb-client

          • 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.
          • Resolved
          is related to

          Bug - A problem that impairs or prevents the functions of the product. WFLY-17218 The jboss-client jar should not shade JBoss Log Manager

          • 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.
          • Closed
          is triggered by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-23805 (7.4.z) Upgrade jboss-ejb-client from 4.0.44.Final-redhat-00001 to 4.0.45.Final-redhat-00001

          • 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.
          • Closed
          relates to

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-24150 (8.0.0.Beta) EJBCLIENT-458 - ConfigurationBasedEJBClientContextSelector should not throw an Error if JBoss Modules is not on the classpath

          • 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

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-24148 [GSS](7.4.z) EJBCLIENT-458 - ConfigurationBasedEJBClientContextSelector should not throw an Error if JBoss Modules is not on the classpath

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

          Activity

            People

              rhn-support-ivassile Ilia Vassilev
              rhn-support-bmaxwell Brad Maxwell
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: