Error executing API request message, sending error response to caller!

[iabshire]

Every 10 seconds the following message appears 5 times in the Application Log: Error executing API request message, sending error response to caller!

Sometimes it goes away, then eventually comes back. These are the surrounding debug/trace messages:

2019-01-14 11:19:19.633-0800 [L: DEBUG] [O: c.t.c.s.c.j.Jsr356ServerConnection] [I: ] [U: ] [S: ] [T: https-jsse-nio-443-exec-10] Receiving BINARY message [ws session id: 7c0] APIRequestMessage [requestId: -1, endpointId: 2687, sessionId: 1605535143, method: GET, entityName: , characteristic: Unknown, target: ]
2019-01-14 11:19:19.633-0800 [L: DEBUG] [O: c.t.c.s.e.DispatchingServerEndpoint] [I: ] [U: ] [S: ] [T: https-jsse-nio-443-exec-10] API REQUEST received [endpoint id: 2979] APIRequestMessage [requestId: -1, endpointId: 2687, sessionId: 1605535143, method: GET, entityName: , characteristic: Unknown, target: ]
2019-01-14 11:19:19.633-0800 [L: TRACE] [O: c.t.c.p.m.DispatchingServerCommunicationModule] [I: ] [U: ] [S: ] [T: https-jsse-nio-443-exec-10] message[com.thingworx.communications.common.messaging.APIRequestMessage]
2019-01-14 11:19:19.633-0800 [L: ERROR] [O: c.t.c.p.m.DispatchingServerCommunicationModule] [I: ] [U: ] [S: ] [T: https-jsse-nio-443-exec-10] Error executing API request message, sending error response to caller!
2019-01-14 11:19:19.633-0800 [L: TRACE] [O: c.t.c.c.e.CommunicationEndpoint] [I: ] [U: ] [S: ] [T: https-jsse-nio-443-exec-10] sending response message [ResponseMessage [requestId: -1, endpointId: 2687, sessionId: 1605535143, code: STATUS_INVALID_SESSION, multipart: false, packet #: 0, total packets: 0]]

Notice that the entityName and target of the APIRequestMessage are empty. Both fields are empty in the Communication Log, as well. It appears the issue is with an invalid session, but how can I determine which agent/web client is the source of this API request?

Thanks!

[MarekP.Nowaczyk · Accepted solution]

Review tomcat localhost_access_log from the same timeframe to see if you can correlate error messages in the Application Log with entries in access_log. Use the IP address in access_log to find out what client makes these requests. This can get more complicated if ThingWorx is behind load balancer as the request will have IP address of the balancer.

[slangley]

Hi @iabshire.

If the response provided by @MarekP.Nowaczyk answered your question, please mark it as the Accepted Solution for the benefit of others with the same question.

Regards.

--Sharon