. I think it is better to leave the
implementation of the fallback mechanism to the failing appender instead of
a general approach which does yield good results under fire.
At 05:41 PM 3/14/2006, Jonathan Beer wrote:
>Hello,
>
>I'm using log4j1.3-alpha8.
>
>I see that in alpha8 the Err
yield good results under fire.
At 05:41 PM 3/14/2006, Jonathan Beer wrote:
>Hello,
>
>I'm using log4j1.3-alpha8.
>
>I see that in alpha8 the ErrorHandler interface has been deprecated.
>
>What is the fallback method that will be used in 1.3 when the appender
>is
Hello,
I'm using log4j1.3-alpha8.
I see that in alpha8 the ErrorHandler interface has been deprecated.
What is the fallback method that will be used in 1.3 when the appender is
not available (for example, with a DBAppender, if the connection is refused,
or with a FileAppender without the prop
Hello,
I am using log4j v1.3alpha-8.
I am attempting to use a DBAppender to append to a MsSQL database (2005
Express).
#1) The MsSQL driver from Microsoft (sqljdbc.jar -
com.microsoft.sqlserver.jdbc.SQLServerDriver) doesn't work with the
DBAppender. Theoretically, it supports the getGeneratedKey
I am wondering if in log4j 1.3 there will be an update to address the
problem identified here:
http://marc.theaimsgroup.com/?l=log4j-user&m=112490801008769&w=2
I have searched the dev and user forums, and haven't found any response to
this query.
I must apologize, this is my first time trying
