[jboss-jira] [JBoss JIRA] Closed: (JBAS-1978) Log4j shutdown patch

[David Lloyd (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBAS-1978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Lloyd closed JBAS-1978.
-----------------------------

    Resolution: Out of Date


Resolved in 6.0 with the new log service.

> Log4j shutdown patch
> --------------------
>
>                 Key: JBAS-1978
>                 URL: https://jira.jboss.org/jira/browse/JBAS-1978
>             Project: JBoss Application Server
>          Issue Type: Patch
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.0.2 Final,  JBossAS-4.0.3RC1
>         Environment: All
>            Reporter: Roelof Naude
>         Attachments: jboss.logging.patch, jboss.logging.patch
>
>   Original Estimate: 30 minutes
>  Remaining Estimate: 30 minutes
>
> Currently the log4j subsystem is not properly shutdown when jboss is shutdown. This cause problems with certain log4j appenders, particularly those that make use of buffering, ie buffered io for file appenders, jdbc appenders with a sizeable internal buffer. The problems experience include:
> 1. when using buffered io, the BufferedWriter is not flushed, resulting in lost messages or only partially written messages
> 2. we have a custom JDBCAppender which only commit (auto commit disabled) after the appender's internal buffer has reach a certain size. currently the appender is not properly closed resulting in lost messages.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira