Uploaded image for project: 'PicketLink'
  1. PicketLink
  2. PLINK-209

Debug/Error inconsistency in exception logging

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Minor Minor
    • PLINK_2.5.3.Beta1
    • PLINK_2.1.X
    • None
    • None

      We came across a strange logging error while testing SOA 6 and it has been tracked down to the combination being used in picketlink. We see this error when DEBUG is enabled even though it is being logged at ERROR level. EAP is using picketlink-core-2.1.6.Final-redhat-2.jar.

      The error is in the log as follows, when DEBUG is enabled

      14:43:41,481 ERROR [org.picketlink.identity.federation] (ServerService Thread Pool – 74) PLFED000259: The provider BC could not be added: java.lang.ClassNotFoundException: org.bouncycastle.jce.provider.BouncyCastleProvider from [Module "org.picketlink:main" from local module loader @1b7ae22 (finder: local module finder @951a0 (roots: /Users/kevin/soa/jboss-eap-6.1/modules,/Users/kevin/soa/jboss-eap-6.1/modules/system/layers/soa,/Users/kevin/soa/jboss-eap-6.1/modules/system/layers/base))]

      The code in question is as below.

      In ProvidersUtil.addJceProvider
      try

      { // Class<? extends Provider> clazz = Loader.loadClass(className, false, Provider.class); Class<? extends Provider> clazz = Class.forName(className).asSubclass(Provider.class); Provider provider = clazz.newInstance(); return addJceProvider(name, provider); }

      catch (Throwable t) {
      ===> if (logger.isDebugEnabled())

      { logger.jceProviderCouldNotBeLoaded(name, t); }

      return null;
      }

      In PicketLinkLoggerMessages

      ==> @LogMessage(level = Level.ERROR)
      @Message(id = 259, value = "The provider %s could not be added")
      void jceProviderCouldNotBeLoaded(String name, @Cause Throwable t);

              psilva@redhat.com Pedro Igor Craveiro
              kconner@redhat.com Kevin Conner (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: