[
https://issues.apache.org/jira/browse/LOG4J2-657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Remko Popma updated LOG4J2-657:
-------------------------------
Fix Version/s: (was: 2.1)
2.0.1
> AbstractDatabaseManager doesn't close connection on writeInternal error
> -----------------------------------------------------------------------
>
> Key: LOG4J2-657
> URL: https://issues.apache.org/jira/browse/LOG4J2-657
> Project: Log4j 2
> Issue Type: Bug
> Components: Appenders
> Affects Versions: 2.0-rc2
> Reporter: Stefan Wehner
> Assignee: Remko Popma
> Fix For: 2.0.1
>
> Attachments: finally.patch
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
