A lot of errors related to Tunnel on every hour

[htran-21]

Hi,

The WSEMS is stopped on the Thing_123, but I could see there are about more than 40.000 errors every hour in ApplicationLog.log, that's significantly downgrading the system's performance. Is there any way to get rid of this error? Tunnel 012a331c-9f11-4dfb-ace0-00002c97ccb4 is not found.

"

2019-02-20 12:56:48.109-0600 [L: ERROR] [O: c.t.w.p.APIProcessor] [I: ] [U: thingworxRead] [S: ] [T: WSExecutionProcessor-4978] Unable to dispatch [ uri = /Things/Thing_123/Services/TunnelCommandFromEdge/]: Unable to Invoke Service TunnelCommandFromEdge on Thing_123: Tunnel 012a331c-9f11-4dfb-ace0-00002c97ccb4 not found

2019-02-20 12:56:48.109-0600 [L: ERROR] [O: c.t.s.s.w.p.WSExecutionInstance] [I: ] [U: ] [S: ] [T: WSExecutionProcessor-4978] error executing APIRequest Message: Unable to dispatch [ uri = /Things/Thing_123/Services/TunnelCommandFromEdge/]: Unable to Invoke Service TunnelCommandFromEdge on Thing_123: Tunnel 012a331c-9f11-4dfb-ace0-00002c97ccb4 not found, sending ERROR ResponseMessage to caller!

"

Any suggestion would be greatly appreciated!

My Bests,

Hung Tran

[slangley]

Hi @htran-21.

We can see in the errors you provided that the user thingworxRead is trying to a service against the remote thing.  We recommend checking for services that are scheduled to run under that user and disabling them until needed.

Regards.

--Sharon

[htran-21]

Hi,

Thank you for your quick response.

I could not find any HTTP request related to "/Things/Thing_123/Services/TunnelCommandFromEdge/" in tomcat access log, but they are in Thingworx Application Log. How is it possible?

My Bests,

Hung Tran

[slangley]

Hi @htran-21.

I'm not sure I understand your confusion.  ThingWorx-related messages are logged to the appropriate log under \ThingworxStorage\logs.

Can you provide more information?

Regards.

[slangley]

Hi @htran-21.

If you have resolved your issue, please post the solution here or select one of the previous replies as the Accepted Solution.

Regards.

--Sharon

[htran-21 · Accepted solution]

Hi Sharon,

This error did not come back when Thingworx is restarted. If you look into the error, the system state was in an infinite loop of trying to re-initialize a NOT_FOUND tunnel. It often happens a few times every 3 months.

"

2019-02-20 12:56:48.109-0600 [L: ERROR] [O: c.t.w.p.APIProcessor] [I: ] [U: thingworxRead] [S: ] [T: WSExecutionProcessor-4978] Unable to dispatch [ uri = /Things/Thing_123/Services/TunnelCommandFromEdge/]: Unable to Invoke Service TunnelCommandFromEdge on Thing_123: Tunnel 012a331c-9f11-4dfb-ace0-00002c97ccb4 not found

2019-02-20 12:56:48.109-0600 [L: ERROR] [O: c.t.s.s.w.p.WSExecutionInstance] [I: ] [U: ] [S: ] [T: WSExecutionProcessor-4978] error executing APIRequest Message: Unable to dispatch [ uri = /Things/Thing_123/Services/TunnelCommandFromEdge/]: Unable to Invoke Service TunnelCommandFromEdge on Thing_123: Tunnel 012a331c-9f11-4dfb-ace0-00002c97ccb4 not found, sending ERROR ResponseMessage to caller!

"

My Bests,

Hung Tran