Franco
(Franco)
November 23, 2019, 3:22pm
21
H102:
From the Karaf console run this command shell:threads --list |grep -i “ruleEngine” and post the output.
You may need to add org.eclipse.smarthome.threadpool:ruleEngine=20 in runtime.cfg if you have system rules that are overloaded.
Im finally able to open the karaf console and executing the command, result is this:
521 x pipe-grep -i “ruleEngine” x TIMED_WAITING x 47 x 30
The delay is gone now but im getting this frequently in the logfile:
2019-11-23 16:20:36.342 [ERROR] [g.discovery.internal.PersistentInbox] - The OSGi lifecycle has been violated (storage: null, ttl checker cancelled: false).
2019-11-23 16:20:36.667 [ERROR] [g.discovery.internal.PersistentInbox] - The OSGi lifecycle has been violated (storage: null, ttl checker cancelled: false).
2019-11-23 16:20:36.998 [ERROR] [g.discovery.internal.PersistentInbox] - The OSGi lifecycle has been violated (storage: null, ttl checker cancelled: false).
H102
(CM6.5 H102)
November 23, 2019, 3:27pm
22
Add this line org.eclipse.smarthome.threadpool:ruleEngine=20 at the bottom in etc/openhab2/services/runtime.cfg (see pic below) then clean cache and reboot.
Are you using VSCode or something other like nano to edit files?
1 Like
Franco
(Franco)
November 23, 2019, 3:41pm
23
You are answering faster then i can react , thanks for your time!
yes, i use VScode. I edited the config, made a clean cache and restart.
The result:
2019-11-23 16:40:14.099 [INFO ] [.eclipse.smarthome.model.script.rule] - start timer
2019-11-23 16:40:44.118 [INFO ] [.eclipse.smarthome.model.script.rule] - timer executed
So happy you saved my day!
1 Like
H102
(CM6.5 H102)
November 23, 2019, 3:44pm
24
@Franco Glad to help!
Please mark the topic solved by clicking the square box on the post that provided the solution.
Thanks