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

AbstractDatabaseManager doesn't close connection on writeInternal error

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 2.0-rc2
    • 2.0.1
    • Appenders
    • None

    Description

      When using the JDBCAppender: if the AbstractDatabaseManager.writeInternal() method fails (e.g. value to large for column size, or any other database error) the database connection is not closed.

      I've attached a proposed patch to fix this - please take a look and see if it makes sense to handle write failures this way.

      Attachments

        1. finally.patch
          1 kB
          Stefan Wehner

        Activity

          People

            rpopma Remko Popma
            stefanwehner Stefan Wehner
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: