09-04-2013 04:03 AM
using sm9.20 since 3 years, recently 2 times it happened, that after a restart of service or reboot the application server
all system processes (agent, linker, change, problem,...) have been started, but do idle and do not restart after 1 minute as normally. Idle time actually is f.e 3 13:5:34 for all system processes which have been started 3 days before whith threadControllerId-background. Trying to kill these processes (and restarting them after) is not successful.
We did not recognize this in time, but after two days users complained, that escalated interactions are still in "Open-Idle" Status, that changes and tasks are not synchronizes and, and, and.
The only "solution" we found: Restart the service on the application server (vertical scaling), but this is a bad solution during working hours.
Is there any way, to reactivate these running but idling processes whithout restart the complete service?
what might be the rootcause of this?
09-04-2013 06:28 AM
thanks for quick answer, but it does not help.
about 1000 entries with class "linker", status in nearly most cases scheduled, sometimes rescheduled, sometimes empty.
scheduled class always empty, action time empty.
I tried several combinations: status rescheduled, class linker, scheduled class linker, set expiration and action time to past dates, but nothing helped. There is no process active to process this new scheduled entries.
The process exists, but he idles and do not know any way to reactivate him
I do not dare to restart f.e. linker process via start scheduler. This will result in two linker processes and I do not know how system might handle to processes with the same name. It might be confused and it is a living system with actual 50 active users.
I will restart the service today in the evening.