[
https://issues.apache.org/jira/browse/LOG4J2-22?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12620988#action_12620988
]
Curt Arnold commented on LOG4J2-22:
-----------------------------------
You do not mention what appender you are using. I'm guessing a JDBCAppender
and I assume that it has no logic to retry if the database is unavailable. It
should however result in a diagnostic message with "Failed to execute sql"
followed by an exception stack trace which should hopefully help you understand
why the operation failed.
> Log4j not doing logging at midnight
> -----------------------------------
>
> Key: LOG4J2-22
> URL: https://issues.apache.org/jira/browse/LOG4J2-22
> Project: Log4j 2
> Issue Type: Bug
> Environment: window server 2000 , using java application , mysql
> database
> Reporter: Gaurav Vaishnava
>
> log4j is not logging at midnight between 23:30 to 00:30 hours.
> in my application at midnight database connection is break so some record not
> processed.
> when i see in logs there are no logs of midnight.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
