What is the reason for the following log messages in the Milo client? How do I handle this exception?

[AriseIGitHub]

What is the reason for the following log messages in the Milo client? How do I handle this exception?

2022-06-29 13:33:05.086 WARN [milo-shared-thread-pool-76] org.eclipse.milo.opcua.stack.client.transport.uasc.UascClientMessageHandler.lambda$onSecureMessage$14.654 No pending request with requestId=90539 for ServiceFault
2022-06-29 13:33:05.087 WARN [milo-shared-thread-pool-76] org.eclipse.milo.opcua.stack.client.transport.uasc.UascClientMessageHandler.lambda$onSecureMessage$14.654 No pending request with requestId=90540 for ServiceFault
2022-06-29 13:37:06.247 WARN [milo-shared-thread-pool-82] org.eclipse.milo.opcua.stack.client.transport.uasc.UascClientMessageHandler.lambda$onSecureMessage$14.654 No pending request with requestId=93488 for ServiceFault
2022-06-29 13:37:06.247 WARN [milo-shared-thread-pool-82] org.eclipse.milo.opcua.stack.client.transport.uasc.UascClientMessageHandler.lambda$onSecureMessage$14.654 No pending request with requestId=93489 for ServiceFault
2022-06-29 13:43:34.297 WARN [milo-shared-thread-pool-87] org.eclipse.milo.opcua.stack.client.transport.uasc.UascClientMessageHandler.lambda$onSecureMessage$14.654 No pending request with requestId=98465 for ServiceFault
2022-06-29 13:43:34.354 WARN [milo-shared-thread-pool-87] org.eclipse.milo.opcua.stack.client.transport.uasc.UascClientMessageHandler.lambda$onSecureMessage$14.654 No pending request with requestId=98466 for ServiceFault
2022-06-29 13:45:34.933 WARN [milo-shared-thread-pool-84] org.eclipse.milo.opcua.stack.client.transport.uasc.UascClientMessageHandler.lambda$onSecureMessage$14.654 No pending request with requestId=99770 for ServiceFault
2022-06-29 13:45:34.979 WARN [milo-shared-thread-pool-84] org.eclipse.milo.opcua.stack.client.transport.uasc.UascClientMessageHandler.lambda$onSecureMessage$14.654 No pending request with requestId=99771 for ServiceFault
2022-06-29 13:46:52.001 WARN [milo-shared-thread-pool-86] org.eclipse.milo.opcua.stack.client.transport.uasc.UascClientMessageHandler.lambda$onSecureMessage$14.654 No pending request with requestId=100435 for ServiceFault
2022-06-29 13:46:52.126 WARN [milo-shared-thread-pool-86] org.eclipse.milo.opcua.stack.client.transport.uasc.UascClientMessageHandler.lambda$onSecureMessage$14.654 No pending request with requestId=100436 for ServiceFault
2022-06-29 13:53:10.147 WARN [milo-shared-thread-pool-92] org.eclipse.milo.opcua.stack.client.transport.uasc.UascClientMessageHandler.lambda$onSecureMessage$14.654 No pending request with requestId=105201 for ServiceFault
2022-06-29 13:53:10.746 WARN [milo-shared-thread-pool-90] org.eclipse.milo.opcua.stack.client.transport.uasc.UascClientMessageHandler.lambda$onSecureMessage$14.654 No pending request with requestId=105202 for ServiceFault

Additional context
System : Centos7.9
milo version : 0.6.6
OPC UA Server :keepserver

[kevinherron]

This means the server you are receiving a response from the server after the request has already timed out and failed on the client side.

The request would have failed due to timeout. If it’s not a request you sent explicitly then it’s probably a PublishRequest the server didn’t respond to in time. There’s nothing else you can do to handle this.

If this happens consistently and you can get a few minutes of Wireshark capture that show both the request and this late response some minutes later we can verify what’s happening.