Strange Delay before rule fires sometimes?

Hello Guys…
I have a strange behaviour on some of my rules… Seems like sometimes there’s a very long delay before a KNX Item receives command untill OH sends the command to KNX - log snip below from yesterday:

2018-09-23 21:56:01.154 [ome.event.ItemCommandEvent] - Item ‘Garage_light_Constant’ received command ON
2018-09-23 21:56:01.154 [vent.ItemStateChangedEvent] - Garage_light_Constant changed from OFF to ON

2018-09-23 21:56:05.938 [ome.event.ItemCommandEvent] - Item ‘Garage_light’ received command ON
2018-09-23 21:56:05.938 [vent.ItemStateChangedEvent] - Garage_light changed from OFF to ON

On the timestamp there’s near 5 seconds delay before it fires the command to turn on the light.,…

What can cauese this? it’s only sometimes this happens - but can be on any rules…

The OH runs on a Windows 10 Intel NUC (Core i3, 16Gb Ram, SSD) can it be hardware missing ressources? The NUC also handles some PFSense firewalling as a Hyper-V instance…

I just think there should be more than enough power to do both

See this thread and try preallocating more memory to Java (but figure out a proper amount of memory suitable for your system, it’s likely a lot more than those 650MB on ARM-32bit quoted there, it rather has to be more like those 3G or 4G like that other guy running on Intel).

Hmm i don’t have access to that topic?

sorry wrong link, now corrected

If Marcus’s link doesn’t provide a solution, look at Why have my Rules stopped running? Why Thread::sleep is a bad idea to see if anything there applies.

Thanks - could be it I think… but how to set these commands when starting up in windows?

@rlkoshak - thanks - gonna run through it - but have only been using timers - no “sleep” commands :slight_smile:

It’s more than just sleeps. Any command that takes more then a few milliseconds and locks can cause problems.

G**gle knows: there’s a column ‘runtime parameters’ in Java system settings/Java