XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Minor Minor
    • 6.0.0.M2
    • None
    • Logging
    • None
    • Low
    • Workaround Exists
    • Hide

      Pretend you don't see the error.

      Show
      Pretend you don't see the error.

      At midnight, we get:

      LogManager error of type WRITE_FAILURE: Error writing log message
      java.io.IOException: Stream closed
      at sun.nio.cs.StreamEncoder.ensureOpen(StreamEncoder.java:26)
      at sun.nio.cs.StreamEncoder.write(StreamEncoder.java:99)
      at sun.nio.cs.StreamEncoder.write(StreamEncoder.java:116)
      at java.io.OutputStreamWriter.write(OutputStreamWriter.java:203)
      at java.io.Writer.write(Writer.java:140)
      at org.jboss.logmanager.handlers.WriterHandler.doPublish(WriterHandler.java:65)
      at org.jboss.logmanager.ExtHandler.publish(ExtHandler.java:59)
      at org.jboss.logmanager.Logger.logRaw(Logger.java:849)
      at org.slf4j.impl.Slf4jLogger.log(Slf4jLogger.java:68)
      at org.apache.commons.logging.impl.SLF4JLocationAwareLog.debug(SLF4JLocationAwareLog.java:120)
      at com.arjuna.common.internal.util.logging.jakarta.JakartaRelevelingLogger.debug(JakartaRelevelingLogger.java:172)
      at com.arjuna.common.internal.util.logging.LogNoi18nImpl.debug(LogNoi18nImpl.java:419)
      at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:727)
      at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:412)

      ...because of an order-of-operations error in the base logmanager handler.

              dlloyd@redhat.com David Lloyd
              dlloyd@redhat.com David Lloyd
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: