Uploaded image for project: 'Log4j 2'
  1. Log4j 2
  2. LOG4J2-407

JDBCAppender cannot recover from loss of database connectivity

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 2.0-beta9
    • 2.0-rc1
    • Appenders
    • None

    Description

      The JDBCAppender holds a single database connection for all its logging. If that database connection is closed, it does not attempt to make a new connection.

      Many connection pools automatically close connections after a certain amount of inactivity. (This can be worked around by properly configuring a pool).

      Database connectivity issues are also common enough that a long running application may experience temporary network issues. When the network comes back online, the logging will not resume.

      I've been meaning to submit a patch for this, but I haven't gotten to it. Since I saw that you are looking to come out of beta soon, I thought I would log this issue in case someone else has time to write the patch before I get to it.

      Attachments

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            beamerblvd Nick Williams
            mikekloster Michael Kloster
            Votes:
            3 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment