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

(8.1.z) [SET] Invalid logger interface com.arjuna.common.logging.commonI18NLogger (implementation not found)

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • None
    • None
    • False
    • Hide

      None

      Show
      None
    • False

      one the errors detected in this jira is:

      node-2 2025-11-04 17:10:08,243 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC000001: Failed to start null: org.jboss.msc.service.StartException in anonymous service: Failed to start service
        at org.jboss.msc@1.5.6.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1545)
        at org.jboss.msc@1.5.6.Final//org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1374)
        at org.jboss.threads@3.9.1//org.jboss.threads.ContextHandler$1.runWith(ContextHandler.java:18)
        at org.jboss.threads@3.9.1//org.jboss.threads.EnhancedQueueExecutor$Task.doRunWith(EnhancedQueueExecutor.java:2651)
        at org.jboss.threads@3.9.1//org.jboss.threads.EnhancedQueueExecutor$Task.run(EnhancedQueueExecutor.java:2630)
        at org.jboss.threads@3.9.1//org.jboss.threads.EnhancedQueueExecutor.runThreadBody(EnhancedQueueExecutor.java:1694)
        at org.jboss.threads@3.9.1//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1589)
        at java.base/java.lang.Thread.run(Thread.java:840)
      Caused by: java.lang.ExceptionInInitializerError
        at org.jboss.jts//com.arjuna.common.internal.util.ClassloadingUtility.loadClass(ClassloadingUtility.java:61)
        at org.jboss.jts//com.arjuna.common.internal.util.ClassloadingUtility.loadAndInstantiateClass(ClassloadingUtility.java:106)
        at org.jboss.jts//com.arjuna.common.internal.util.ClassloadingUtility.loadAndInstantiateClass(ClassloadingUtility.java:98)
        at org.jboss.jts//com.arjuna.common.internal.util.ClassloadingUtility.loadAndInstantiateClassesWithInit(ClassloadingUtility.java:199)
        at org.jboss.jts//com.arjuna.ats.arjuna.common.RecoveryEnvironmentBean.getRecoveryModules(RecoveryEnvironmentBean.java:423)
        at org.jboss.jts//com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.loadModules(PeriodicRecovery.java:907)
        at org.jboss.jts//com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.<init>(PeriodicRecovery.java:88)
        at org.jboss.jts//com.arjuna.ats.internal.arjuna.recovery.RecoveryManagerImple.<init>(RecoveryManagerImple.java:70)
        at org.jboss.jts//com.arjuna.ats.arjuna.recovery.RecoveryManager.<init>(RecoveryManager.java:408)
        at org.jboss.jts//com.arjuna.ats.arjuna.recovery.RecoveryManager.manager(RecoveryManager.java:91)
        at org.jboss.jts//com.arjuna.ats.arjuna.recovery.RecoveryManager.manager(RecoveryManager.java:75)
        at org.jboss.jts.integration@7.3.2.Final//com.arjuna.ats.jbossatx.jta.RecoveryManagerService.create(RecoveryManagerService.java:37)
        at org.jboss.as.transactions@39.0.0.Beta1-SNAPSHOT//org.jboss.as.txn.service.ArjunaRecoveryManagerService.start(ArjunaRecoveryManagerService.java:126)
        at org.jboss.msc@1.5.6.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1553)
        at org.jboss.msc@1.5.6.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1516)
        ... 7 more
      Caused by: java.lang.IllegalArgumentException: Invalid logger interface com.arjuna.common.logging.commonI18NLogger (implementation not found)
        at org.jboss.logging@3.6.1.Final//org.jboss.logging.Logger.doGetMessageLogger(Logger.java:2630)
        at org.jboss.logging@3.6.1.Final//org.jboss.logging.Logger.getMessageLogger(Logger.java:2536)
        at org.jboss.logging@3.6.1.Final//org.jboss.logging.Logger.getMessageLogger(Logger.java:2521)
        at org.jboss.jts//com.arjuna.common.logging.commonLogger.<clinit>(commonLogger.java:16)
      

      this was fixed in
      https://github.com/jbosstm/narayana/commit/109df3f48f50b17497e837e34838593d1ce2cf6a

      which is included in 7.3.3
      current version in manifest is
      https://gitlab.cee.redhat.com/jboss-set/proposed-manifests/jboss-eap-8.1-proposed-manifests/-/blob/main/manifest.yaml?ref_type=heads#L1154

       groupId: "org.jboss.narayana.jts"
          artifactId: "narayana-jts-idlj"
          version: "7.1.2.Final-redhat-00001"
      

      It has verified that
      https://maven.repository.redhat.com/ga/org/jboss/narayana/jts/narayana-jts-idlj/7.1.2.Final-redhat-00001/narayana-jts-idlj-7.1.2.Final-redhat-00001.jar

      observerd in here:
      https://ci.wildfly.org/test/1847924361860593795?currentProjectId=WF_PullRequest

      contains the processor logging activated.
      Maybe it is a class loading problem

              rhn-support-egonzale Enrique Gonzalez Martinez
              rhn-support-egonzale Enrique Gonzalez Martinez
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: