[
https://issues.apache.org/jira/browse/IGNITE-2173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15058392#comment-15058392
]
Alexey Kuznetsov edited comment on IGNITE-2173 at 12/15/15 5:40 PM:
--------------------------------------------------------------------
Micael, this was an issue in ignite-1.4 release, but I fixed that in ignite-1.5
code base several weeks ago.
Could you recheck?
See:
https://github.com/apache/ignite/blob/ignite-1.5/modules/core/src/main/java/org/apache/ignite/cache/store/jdbc/CacheAbstractJdbcStore.java
log.debug() is now protected with log.isDebugEnabled()
was (Author: kuaw26):
Micael, this was an issue in ignite-1.4 release, but I fixed that in ignite-1.5
code base.
Could you recheck?
See:
https://github.com/apache/ignite/blob/ignite-1.5/modules/core/src/main/java/org/apache/ignite/cache/store/jdbc/CacheAbstractJdbcStore.java
log.debug() is now protected with log.isDebugEnabled()
> Some log.debug() calls in CacheAbstractJdbcStore.java are not protected with
> if (log.isDebugEnabled())
> ------------------------------------------------------------------------------------------------------
>
> Key: IGNITE-2173
> URL: https://issues.apache.org/jira/browse/IGNITE-2173
> Project: Ignite
> Issue Type: Bug
> Components: cache
> Affects Versions: 1.5
> Reporter: Michael Griggs
> Assignee: Michael Griggs
> Priority: Minor
> Fix For: 1.6
>
>
> e.g., line 1029
> {code}
> log.debug("Write entries to db one by one using update and insert statements
> [cache name=" +
> {code}
> A side-effect of this is WARNing messages in your log file when these
> statements are executed:
> {code}
> 2015-12-15 16:19:26 WARN CacheJdbcPojoStore:463 - Logging at DEBUG level
> without checking if DEBUG level is enabled:
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
