Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

set the loggerName of the locally generated LogRecords (#1167) #1188

Merged
merged 1 commit into from May 11, 2018

Conversation

@kommiharibabu
Copy link
Contributor

@kommiharibabu kommiharibabu commented May 11, 2018

In ConnectionFactoryImpl.log function locally generates the logRecord
but doesn't set the loggerName of the current Logger, as a result
the log ignores the class or package level logging configuration

In ConnectionFactoryImpl.log function locally generates the logRecord
but doesn't set the loggerName of the current Logger, as a result
the log ignores the class or package level logging configuration
@vlsi vlsi added this to the 42.2.3 milestone May 11, 2018
@vlsi vlsi merged commit f78a639 into pgjdbc:master May 11, 2018
1 check was pending
1 check was pending
continuous-integration/travis-ci/pr The Travis CI build is in progress
Details
@kommiharibabu kommiharibabu deleted the kommiharibabu:issue_1167 branch May 11, 2018
rhavermans added a commit to bolcom/pgjdbc that referenced this pull request Jul 13, 2018
In ConnectionFactoryImpl.log function locally generates the logRecord
but doesn't set the loggerName of the current Logger, as a result
the log ignores the class or package level logging configuration

fixes pgjdbc#1167
rhavermans added a commit to bolcom/pgjdbc that referenced this pull request Jul 13, 2018
In ConnectionFactoryImpl.log function locally generates the logRecord
but doesn't set the loggerName of the current Logger, as a result
the log ignores the class or package level logging configuration

fixes pgjdbc#1167
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

2 participants
You can’t perform that action at this time.