[
https://issues.apache.org/jira/browse/IGNITE-8899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16527874#comment-16527874
]
ASF GitHub Bot commented on IGNITE-8899:
----------------------------------------
GitHub user ezhuravl opened a pull request:
https://github.com/apache/ignite/pull/4284
IGNITE-8899 remove creating JavaLogger in static context in IgniteJdb…
…cDriver
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8899
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/4284.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #4284
----
commit a2f5910d33ee15d5f8777666f7f68a64bf043d1a
Author: ezhuravl <ezhuravlev@...>
Date: 2018-06-29T15:59:16Z
IGNITE-8899 remove creating JavaLogger in static context in IgniteJdbcDriver
----
> IgniteJdbcDriver directly create JavaLogger in static context
> -------------------------------------------------------------
>
> Key: IGNITE-8899
> URL: https://issues.apache.org/jira/browse/IGNITE-8899
> Project: Ignite
> Issue Type: Bug
> Reporter: Evgenii Zhuravlev
> Assignee: Evgenii Zhuravlev
> Priority: Major
>
> It means, that it always prints error in logs, if Jul logging file doesn't
> exist. I suggest to use the same approach as in thin driver:
> replace
> new JavaLogger()
> with
> Logger.getLogger(IgniteJdbcDriver.class.getName())
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
