View Revisions: Issue #6209
| Summary | 0006209: "Node failed to authenticate" in server logs after server restarts or client session expires | ||
|---|---|---|---|
| Revision | 2024-01-25 21:02 by elong | ||
| Description | When a client node's authenticated session expires, or if the server is restarted, the server log may contain: Node 'X' failed to authenticate. It is missing the security token The client log might contain: DataLoaderService - Failed to process incoming batch from node 'Y': AuthenticationExpiredException The client re-authenticates and recovers, but the logging makes it sound like there is a problem. With channel queues, several of the log entries can appear. It also seems to be removing the session and forcing a new one to be created instead of renewing the existing session. |
||
| Revision | 2024-01-25 20:56 by elong | ||
| Description | When a client node's authenticated session expires, or if the server is restarted, the server log may contain: Node 'X' failed to authenticate. It is missing the security token The client log might contain: DataLoaderService - Failed to process incoming batch from node 'Retail_1': AuthenticationExpiredException The client re-authenticates and recovers, but the logging makes it sound like there is a problem. With channel queues, several of the log entries can appear. It also seems to be removing the session and forcing a new one to be created instead of renewing the existing session. |
||