"Don't know how to process exit" seen on Background MS

[avillanueva]

2023-05-29 11:12:51,345 ERROR [Thread-123 ProcessMessages] wt.wvs.workeragent.ProcessMessages  - Don't know how to process exit

I am seeing this repeated message in my BGMS. Over holiday, it was written every 20-30 mins. We also had an issue with the BGMS where it was locking up, no queue jobs were processing and restart was done. I am wondering if this is related.  When I checked Server Status Max and Avg concurrency was red for the BGMS.

[joe_morton]

No clue.. but what comes to mind is antivirus software. Check to see if it might be possibly locking files?

[avillanueva]

It seems to be part of a normal CAD Agent exception messages. This is something similar:

https://www.ptc.com/en/support/article/CS329282?source=search

What's strange is that is runs like a polling process every 20 seconds or so.

[HelesicPetr]

Hi @avillanueva 

Do you know what queue case the error? wvs, wokrflow, or some other queues?

What else the error shows? Other rows with at and so on.  Where the error is thrown can be the key. 

PetrH

[avillanueva]

Its in the Background MS, I was mistaken that it was 20-30 minutes, its seconds:

2023-06-06 07:03:40,705 ERROR [Thread-17696 ProcessMessages] wt.wvs.workeragent.ProcessMessages  - Don't know how to process exit
2023-06-06 07:03:55,705 ERROR [Thread-17697 ProcessMessages] wt.wvs.workeragent.ProcessMessages  - Don't know how to process exit
2023-06-06 07:04:10,705 ERROR [Thread-17698 ProcessMessages] wt.wvs.workeragent.ProcessMessages  - Don't know how to process exit
2023-06-06 07:04:25,704 ERROR [Thread-17699 ProcessMessages] wt.wvs.workeragent.ProcessMessages  - Don't know how to process exit
2023-06-06 07:04:40,705 ERROR [Thread-17704 ProcessMessages] wt.wvs.workeragent.ProcessMessages  - Don't know how to process exit
2023-06-06 07:04:55,705 ERROR [Thread-17705 ProcessMessages] wt.wvs.workeragent.ProcessMessages  - Don't know how to process exit
2023-06-06 07:05:10,705 ERROR [Thread-17706 ProcessMessages] wt.wvs.workeragent.ProcessMessages  - Don't know how to process exit
2023-06-06 07:05:25,704 ERROR [Thread-17707 ProcessMessages] wt.wvs.workeragent.ProcessMessages  - Don't know how to process exit
2023-06-06 07:05:40,704 ERROR [Thread-17708 ProcessMessages] wt.wvs.workeragent.ProcessMessages  - Don't know how to process exit
2023-06-06 07:05:55,705 ERROR [Thread-17709 ProcessMessages] wt.wvs.workeragent.ProcessMessages  - Don't know how to process exit
2023-06-06 07:06:10,705 ERROR [Thread-17710 ProcessMessages] wt.wvs.workeragent.ProcessMessages  - Don't know how to process exit
2023-06-06 07:06:25,705 ERROR [Thread-17711 ProcessMessages] wt.wvs.workeragent.ProcessMessages  - Don't know how to process exit

You would think this would be a job in the publishing queue but all jobs are complete. Looks like this is a polling process by CAD Agent?

[HelesicPetr]

Hi @avillanueva 

I would try to set debug for the wt.wvs.workeragent.ProcessMessages logger 

It is very specific that I guess something is in never ending loop and it always ends with this message

PetrH

[avillanueva]

They did not make this easy. I was able to find this code in com.ptc.wvs.server.cadagent package (buried in a jar). They neglected to change the logger name (for shame!).

private static final WVSLogger logger = WVSLogger.getLogger(ProcessMessages.class, "wt.wvs.workeragent");

The message I am seeing is defined in cadagentResource.class:

@RBEntry("Don't know how to process {0}")
	public static final String ERROR_PROCESSING_MESSAGE = "32";

There isn't a whole lot of logger messages in this but it appears to be the CAD agent process that reads a socket a processes messages. 

2023-06-06 07:46:25,706 ERROR [Thread-17934 ProcessMessages] wt.wvs.workeragent.ProcessMessages  - Don't know how to process exit
2023-06-06 07:46:25,706 DEBUG [Thread-17934 ProcessMessages] wt.wvs.workeragent.ProcessMessages  - Returned <TERMINATED>
2023-06-06 07:46:40,707 DEBUG [Thread-17935 ProcessMessages] wt.wvs.workeragent.ProcessMessages  - Returned exit

[HelesicPetr]

@avillanueva 

If you debug in your develop ide (eclipse, whatever) and stops the process on the specific line, can you see previous process and variables? my ide can do it and thanks that I can find root case in some situations. 

so you can find a root process where it comes from.. 

PetrH

[avillanueva · Accepted solution]

We used tcpdump to trace traffic back to a watchtower monitoring service. We believe it was the cause since in checking for the open port as proof WVS Services are functioning properly, it cause the agent to process garbage. Still confirming but I will close this thread if that is the case. 

[avillanueva]

Confirmed, it was a ping process. We adjusted to a longer interval but that was the source. The vendor has not seen this behavior before but is working with PTC on better ways to monitor WVS services remotely.