Community Tip - Visit the PTCooler (the community lounge) to get to know your fellow community members and check out some of Dale's Friday Humor posts! X
Hi,
I'm following the guide https://developer.thingworx.com/resources/guides/anomaly-detection-how-guide . During the model training it fails after calibrating and the application log throws out this error multiple times
Not really sure what the issue could be. Both the training and results microservices are up and running. Thanks.
Solved! Go to Solution.
Hi
The error you get is documented at https://www.ptc.com/en/support/article?n=CS269383.
You need to allocate more memory to the JVM of training and result microservices.
The above article gives the steps to do so.
Kind rgeards
Christophe
Which version of the microservices are you running?
Where is the ThingWorx Core server running, and where are the microservices running? The TW Core server must be able to make a network connection to the microservices.
Do you see anything in microservices console window?
I'm running the 2.0.2 version result microservice and 2.0.4 of the training microservice. I've installed the Thingworx Trial Edition in Docker. I've attached the logs for both the training and result microservices.
Hi
The error you get is documented at https://www.ptc.com/en/support/article?n=CS269383.
You need to allocate more memory to the JVM of training and result microservices.
The above article gives the steps to do so.
Kind rgeards
Christophe
Yes thanks for your help. I had to allocate a lot more memory for the microservices and I used that article.
Hi
it probably would be useful to see the ThingWorx log file and mostly the training and result microservice log too (see https://www.ptc.com/en/support/article?n=CS266118 if they are not created by default).
However a common mistake is with the syntax of file.storage.path property.
Do check Configure File Path at https://developer.thingworx.com/resources/guides/anomaly-detection-how-guide/set-and-run-thingwatcher-micro-services .
You probably are having a version 2.0.5 or later so need to use the correct syntax.
Hope this helps
Christophe
Yes the syntax of file.storage.path is also correct. I've attached the log files.