geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GEODE-4958) Remove stack trace logging for some occurrences of AuthenticationRequiredException
Date Wed, 03 Jul 2019 18:55:00 GMT

    [ https://issues.apache.org/jira/browse/GEODE-4958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16878084#comment-16878084
] 

ASF subversion and git services commented on GEODE-4958:
--------------------------------------------------------

Commit c46039198f30c411c05c9dcc28615005b87cbf63 in geode's branch refs/heads/develop from
Naburun Nag
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=c460391 ]

GEODE-4958: Reducing log level to warn

	* This code change from a previous commit was lost due to a merge from GEODE-6626.
	* This commit is to bring back that change.


> Remove stack trace logging for some occurrences of AuthenticationRequiredException
> ----------------------------------------------------------------------------------
>
>                 Key: GEODE-4958
>                 URL: https://issues.apache.org/jira/browse/GEODE-4958
>             Project: Geode
>          Issue Type: Improvement
>          Components: security
>            Reporter: Jens Deppe
>            Priority: Major
>             Fix For: 1.10.0
>
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> Occasionally we're logging messages like these:
> {noformat}
> ```[error 2018/03/27 17:05:19.471 CST server2 <ServerConnection on port 40404 Thread
632> tid=0x2ec] Failed to bind the subject of uniqueId -5320790194368010384 for message
REQUEST with Server connection from [identity(0.0.0.0(default_GeodeDS:177342:loner):2:GFNative_9Vy9zzNsTw177342:default_GeodeDS,connection=1;
port=35644]
> [warning 2018/03/27 17:05:19.472 CST server2 <ServerConnection on port 40404 Thread
632> tid=0x2ec] ClientHealthMonitor: Unregistering client with member id identity(0.0.0.0(default_GeodeDS:177342:loner):2:GFNative_9Vy9zzNsTw177342:default_GeodeDS,connection=1
due to: Unknown reason
> [severe 2018/03/27 17:05:19.475 CST server2 <ServerConnection on port 40404 Thread
632> tid=0x2ec] Uncaught exception in thread Thread[ServerConnection on port 40404 Thread
632,5,ServerConnection on port 40404]
> org.apache.geode.security.AuthenticationRequiredException: Failed to find the authenticated
user.
>     at org.apache.geode.internal.cache.tier.sockets.ServerConnection.doNormalMsg(ServerConnection.java:793)
>     at org.apache.geode.internal.cache.tier.sockets.LegacyServerConnection.doOneMessage(LegacyServerConnection.java:85)
>     at org.apache.geode.internal.cache.tier.sockets.ServerConnection.run(ServerConnection.java:1179)
>     at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>     at org.apache.geode.internal.cache.tier.sockets.AcceptorImpl$4$1.run(AcceptorImpl.java:641)
>     at java.lang.Thread.run(Thread.java:748)
> [error 2018/03/27 17:05:25.575 CST server2 <ServerConnection on port 40404 Thread
640> tid=0x2f4] Failed to bind the subject of uniqueId -8780376006667518716 for message
REQUEST with Server connection from [identity(0.0.0.0(default_GeodeDS:177266:loner):2:GFNative_QCAzJikbYT177266:default_GeodeDS,connection=1;
port=36288]
> [warning 2018/03/27 17:05:25.576 CST server2 <ServerConnection on port 40404 Thread
640> tid=0x2f4] ClientHealthMonitor: Unregistering client with member id identity(0.0.0.0(default_GeodeDS:177266:loner):2:GFNative_QCAzJikbYT177266:default_GeodeDS,connection=1
due to: Unknown reason
> [severe 2018/03/27 17:05:25.577 CST server2 <ServerConnection on port 40404 Thread
640> tid=0x2f4] Uncaught exception in thread Thread[ServerConnection on port 40404 Thread
640,5,ServerConnection on port 40404]
> org.apache.geode.security.AuthenticationRequiredException: Failed to find the authenticated
user.
>     at org.apache.geode.internal.cache.tier.sockets.ServerConnection.doNormalMsg(ServerConnection.java:793)
>     at org.apache.geode.internal.cache.tier.sockets.LegacyServerConnection.doOneMessage(LegacyServerConnection.java:85)
>     at org.apache.geode.internal.cache.tier.sockets.ServerConnection.run(ServerConnection.java:1179)
>     at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>     at org.apache.geode.internal.cache.tier.sockets.AcceptorImpl$4$1.run(AcceptorImpl.java:641)
>     at java.lang.Thread.run(Thread.java:748)```
> {noformat}
> They look scary but we should remove the stack trace from the log - the severity can
also be turned down to 'warning'.
> This is related to GEODE-4076



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message