[
https://issues.apache.org/jira/browse/IGNITE-19421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17719910#comment-17719910
]
Nikita Amelchev commented on IGNITE-19421:
------------------------------------------
Added extended logging on debug level:
{noformat}
<Logger
name="org.apache.ignite.internal.processors.odbc.ClientListenerNioListener"
level="DEBUG"/>
{noformat}
Logging of each request moved to a trace level.
Example of output:
- Success client
{noformat}
[ClientListenerNioListener] Client connected: /127.0.0.1:54974
[ClientListenerNioListener] Client handshake accepted
[rmtAddr=/127.0.0.1:54974, type=thin, ver=1.7.0, login=client1,
connId=8589934596]
...
[ClientListenerNioListener] Client disconnected: /127.0.0.1:54974
{noformat}
- Failed client
{noformat}
[ClientListenerNioListener] Client connected: /127.0.0.1:54952
[ClientListenerNioListener] Client authentication failed
[rmtAddr=/127.0.0.1:54952, type=thin, ver=1.7.0, err=The user name or password
is incorrect [userName=client1]]
[ClientListenerNioListener] Client disconnected: /127.0.0.1:54952
18:26
{noformat}
> Add extended logging of client connections
> -------------------------------------------
>
> Key: IGNITE-19421
> URL: https://issues.apache.org/jira/browse/IGNITE-19421
> Project: Ignite
> Issue Type: Task
> Reporter: Nikita Amelchev
> Assignee: Nikita Amelchev
> Priority: Minor
> Labels: ise
> Fix For: 2.16
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> I propose to add extended logging(debug level) of client connections to debug
> network issues per client:
> - add client info: type, version, login
> - move request's logging to trace level.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
