Timer disable timer service

[XZ_13333181]

I am using ThingWorx Platform Release 9.5 and DatecodeSP5

Timer The Disable Timer service shows no response. There was no error reported in the log either. And Enable Stack Tracing

[TonyZhang]

Hi @XZ_13333181,

What do you mean by "shows no response"? Do you get "No results" as the Output after executing DisableTimer service?

Can you check the Enabled property of the Timer Thing? Is it set to false (unchecked)?

If the Enabled property is set to true, can you manually edit the property value and set it to false?

[XZ_13333181]

After clicking "Execute" in the Disable Timer service, it shows "Executing" status.

The attribute "enable" shows "true", and attempting to change it to "false" fails.

General Information  "Automatically Enable Timer on Startup"show "enable" 

[TonyZhang]

Can you try unchecking "Automatically Enable Timer on Startup Running" and running RestartThing service?

Is this issue only observed with a particular Timer or all/multiple timers are affected?

If that doesn't work, try restarting Tomcat service or deleting this Timer and creating a new Timer to see if it resolves the issue?

[XZ_13333181]

“RestartThing”The service is operating normally but there are no results displayed.

 All timers have this problem.

Discovered ,The enablement and disabling services for the timer and the scheduler are both unavailable.

[TonyZhang]

Hi @XZ_13333181,

Can you export an affected timer entity as xml, reproduce the issue again by running the affected enablement and disabling services of the exported timer, then attach all the logs under /ThingworxStorage/logs for further investigation?

> “RestartThing” service is operating normally but there are no results displayed.

↑ FYI, returning no results is expected because all it does is restarting things, no need to return any value, if it runs successfully it will return no results

What I wanted you to check is whether unchecking "Automatically Enable Timer on Startup Running" and saving it (restarting thing is just to make sure the configuration change is reflected) can disable the Timer - to achieve what you want.

Also, please make sure you have proper User configured as the Run As User for Timers

[XZ_13333181]

Hi,Tony

Export the Timer entity from the production environment to XML. Then, in the non-production environment, test the disabling of the timer service. It was found that the service can be used normally.

"Automatically Enable Timer on Startup Running"Unselect,The problem still exists.

Checking the nginx log shows an error of 10060.

Checking the Thingworx ApplicationLog revealed an error related to ignite.:class org.apache.ignite.IgniteCheckedException: Failed to update keys on primary node.

[TonyZhang · Accepted solution]

Hi @XZ_13333181,

Good, with the error message I guess you have some clue to continue troubleshooting the issue.

Make sure you have ignite which version is compatible with ThingWorx if you are using external ignite (client mode: true)

https://release-advisor.ptc.com/releaseMatrix?releaseId=2055

Also, you can refer to the configuration of your non-production environment which is working.

If you still need assistance, please attach the logs, config files and more information on your HA implementation/architectual setup.

I would suggest you raise a support case to have a technical support help you troubleshooting such issues.

[XZ_13333181]

Hi，Tony

Thank you for your support.

I will create cases to obtain support.