Log4j 2
  1. Log4j 2
  2. LOG4J2-407

JDBCAppender cannot recover from loss of database connectivity

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 2.0-beta9
    • Fix Version/s: 2.0-rc1
    • Component/s: Appenders
    • Labels:
      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.

        Issue Links

          Activity

            People

            • Assignee:
              Nick Williams
              Reporter:
              Michael Kloster
            • Votes:
              3 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development