Uploaded image for project: 'Red Hat Data Grid'
  1. Red Hat Data Grid
  2. JDG-1220

JDG 7.1.0 logging is not compatible with EAP 7.1.0.DR16+

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Critical
    • JDG 7.1.1 CR2
    • JDG 7.1.0 GA, JDG 7.1.1 CR1, JDG 7.1.1 ER1
    • Build/Packaging
    • None
    • Release Notes, Compatibility/Configuration
    • CR2
    • Workaround Exists
    • Hide

      Use the recommended JDG modules instead of packaging the library within the application archive.

      Show
      Use the recommended JDG modules instead of packaging the library within the application archive.
    • Hide

      Any JDG application which include the library.jar directly

      Show
      Any JDG application which include the library.jar directly

    Description

      EAP include an upgrade of jboss-logging (3.3.0->3.3.1) but JDG includes jboss-logging 3.3.0.
      Both versions are not compatible and the deployment will fail with the following message.

      Caused by: java.lang.Exception: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"test.war\".WeldStartService" => "Failed to start service
      Caused by: org.jboss.weld.exceptions.DeploymentException: tried to access class org.jboss.logging.Log4j2Logger from class org.jboss.logging.Log4j2Logger$1
      Caused by: java.lang.IllegalAccessError: tried to access class org.jboss.logging.Log4j2Logger from class org.jboss.logging.Log4j2Logger$1"}}
      at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.getActionResult(ServerDeploymentPlanResultFuture.java:134)
      at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.getResultFromNode(ServerDeploymentPlanResultFuture.java:123)
      at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.get(ServerDeploymentPlanResultFuture.java:85)
      at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.get(ServerDeploymentPlanResultFuture.java:42)
      at org.jboss.as.controller.client.helpers.standalone.ServerDeploymentHelper.deploy(ServerDeploymentHelper.java:55)
      at org.jboss.as.arquillian.container.ArchiveDeployer.deployInternal(ArchiveDeployer.java:77)
      at org.jboss.as.arquillian.container.ArchiveDeployer.deployInternal(ArchiveDeployer.java:64)
      at org.jboss.as.arquillian.container.ArchiveDeployer.deploy(ArchiveDeployer.java:46)

      Attachments

        Issue Links

          incorporates

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-12297 JDG 7.1.0 is incompatible with EAP 7.1.0.DR16

          • 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

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-12567 JDG 7.1.0 is incompatible with jboss-logging 3.3.1 while it works with 3.3.0

          • 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
          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. JDG-1221 JBoss logging should be compatible to be able to deploy JDG 7.2 in JBoss EAP 7.1.x

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

          Activity

            People

              jsenko@redhat.com Jakub Senko
              rhn-support-wfink Wolf Fink
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: