Log4j 2
  1. Log4j 2
  2. LOG4J2-178

Build broken: FlumePersistentAppenderTest fails because of java.security.InvalidKeyExceptions

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 2.0-beta5
    • Fix Version/s: 2.0-beta5
    • Component/s: None
    • Labels:
      None

      Description

      from the Maven output:
      Tests run: 18, Failures: 0, Errors: 4, Skipped: 0

      [INFO] ------------------------------------------------------------------------
      [INFO] Reactor Summary:
      [INFO]
      [INFO] Apache Log4j 2 .................................... SUCCESS [1.470s]
      [INFO] Apache Log4j API .................................. SUCCESS [11.678s]
      [INFO] Apache Log4J Core ................................. SUCCESS [2:28.445s]
      [INFO] Apache Log4j 1.x Compatibility API ................ SUCCESS [5.078s]
      [INFO] Apache Log4j SLF4J Binding ........................ SUCCESS [3.871s]
      [INFO] Apache Log4j to SLF4J Adapter ..................... SUCCESS [2.386s]
      [INFO] Apache Log4j Commons Logging Bridge ............... SUCCESS [2.818s]
      [INFO] Apache Log4j Flume NG Bridge ...................... FAILURE [44.447s]
      [INFO] Log4j Web Adapters ................................ SKIPPED
      [INFO] log4j-samples ..................................... SKIPPED
      [INFO] flume-common ...................................... SKIPPED
      [INFO] flume-remote ...................................... SKIPPED
      [INFO] flume-embedded .................................... SKIPPED
      [INFO] Apache Log4j Async ................................ SKIPPED
      [INFO] ------------------------------------------------------------------------
      [INFO] BUILD FAILURE
      [INFO] ------------------------------------------------------------------------

      Tests in error:
      testMultiple(org.apache.logging.log4j.flume.appender.FlumePersistentAppenderTest): An exception occurred processing Appender eventLogger
      testFailover(org.apache.logging.log4j.flume.appender.FlumePersistentAppenderTest): An exception occurred processing Appender eventLogger
      testLog4Event(org.apache.logging.log4j.flume.appender.FlumePersistentAppenderTest): An exception occurred processing Appender eventLogger
      testPerformance(org.apache.logging.log4j.flume.appender.FlumePersistentAppenderTest): An exception occurred processing Appender eventLogger

      Running org.apache.logging.log4j.flume.appender.FlumePersistentAppenderTest
      2013-03-20 15:00:30,323 ERROR An exception occurred processing Appender eventLogger org.apache.logging.log4j.LoggingException: Exception occurred writing log event
      at org.apache.logging.log4j.flume.appender.FlumePersistentManager.send(FlumePersistentManager.java:167)
      at org.apache.logging.log4j.flume.appender.FlumeAppender.append(FlumeAppender.java:90)
      at org.apache.logging.log4j.core.config.AppenderControl.callAppender(AppenderControl.java:102)
      at org.apache.logging.log4j.core.config.LoggerConfig.callAppenders(LoggerConfig.java:366)
      at org.apache.logging.log4j.core.config.LoggerConfig.log(LoggerConfig.java:347)
      at org.apache.logging.log4j.core.config.LoggerConfig.log(LoggerConfig.java:310)
      at org.apache.logging.log4j.core.Logger.log(Logger.java:108)
      at org.apache.logging.log4j.spi.AbstractLoggerWrapper.log(AbstractLoggerWrapper.java:55)
      at org.apache.logging.log4j.EventLogger.logEvent(EventLogger.java:54)
      at org.apache.logging.log4j.flume.appender.FlumePersistentAppenderTest.testMultiple(FlumePersistentAppenderTest.java:145)
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
      at java.lang.reflect.Method.invoke(Method.java:601)
      at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
      at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
      at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
      at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
      at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
      at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
      at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:76)
      at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
      at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
      at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
      at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
      at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
      at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
      at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
      at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
      at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
      at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:252)
      at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:141)
      at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112)
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
      at java.lang.reflect.Method.invoke(Method.java:601)
      at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
      at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
      at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
      at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115)
      at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)
      Caused by: java.security.InvalidKeyException: Illegal key size or default parameters
      at javax.crypto.Cipher.checkCryptoPerm(Cipher.java:1011)
      at javax.crypto.Cipher.implInit(Cipher.java:786)
      at javax.crypto.Cipher.chooseProvider(Cipher.java:849)
      at javax.crypto.Cipher.init(Cipher.java:1213)
      at javax.crypto.Cipher.init(Cipher.java:1153)
      at org.apache.logging.log4j.flume.appender.FlumePersistentManager.send(FlumePersistentManager.java:159)
      ... 41 more

        Activity

        Hide
        Remko Popma added a comment -

        Confirmed this problem no longer occurs.

        Show
        Remko Popma added a comment - Confirmed this problem no longer occurs.
        Hide
        Ralph Goers added a comment -

        Test for encryption is now disabled by default.

        Show
        Ralph Goers added a comment - Test for encryption is now disabled by default.
        Hide
        Ralph Goers added a comment - - edited

        This error is most likely due to the JDK not having the proper encryption support installed. I will probably have to disable encryption in the tests to keep this from happening. See http://stackoverflow.com/questions/6481627/java-security-illegal-key-size-or-default-parameters

        Show
        Ralph Goers added a comment - - edited This error is most likely due to the JDK not having the proper encryption support installed. I will probably have to disable encryption in the tests to keep this from happening. See http://stackoverflow.com/questions/6481627/java-security-illegal-key-size-or-default-parameters

          People

          • Assignee:
            Unassigned
            Reporter:
            Remko Popma
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development