Eclipse Community Forums: Eclipse SmartHome » Remove Quartz in favour of ScheduledExecutorService

Help

Home

Home » Archived » Eclipse SmartHome » Remove Quartz in favour of ScheduledExecutorService

Show: Today's Messages :: Show Polls :: Message Navigator

Remove Quartz in favour of ScheduledExecutorService [message #1705818]

Wed, 19 August 2015 11:06

Karel Goderis

Messages: 198
Registered: March 2014

Senior Member

In OpenHAB 1 Quartz was introduced to allow easy cronjob-like scheduling for Rules

I am wondering if we should get rid of Quartz all together, and move as much functionality onto the ThreadPoolManager provided schedulers? As a bonus it would reduce the memory footprint of ESH/OH

With respect to the "cron" aspect of things, we could revert back to the CronExpression class of Quartz itself, or rely on external implementations like http://jarretttaylor.com/java/jt-cron.html or https://github.com/anderswisch/cron-expression

Any thoughts?

Karel

Report message to a moderator

Re: Remove Quartz in favour of ScheduledExecutorService [message #1705891 is a reply to message #1705818]

Wed, 19 August 2015 20:35

Dennis Nobel

Messages: 166
Registered: September 2014

Senior Member

I think Quartz is doing a lot more then just executing a Task based on a cron expression. Not sure what is used actually used. With the new rule engine there is a chance to get rid off it. The scheduling is not yet implemented. But Quartz is only about 700kb, so I don´t see a big problem here.

Regards

Dennis

Report message to a moderator

Re: Remove Quartz in favour of ScheduledExecutorService [message #1705900 is a reply to message #1705891]

Wed, 19 August 2015 22:14

Karel Goderis

Messages: 198
Registered: March 2014

Senior Member

Indeed, but at the time of OH1 I ran into a lot of issues with Quartz when developing the Sonos binding. I simply could not keep up with high rate job scheduling.

It is also used in the persistence packages.

Report message to a moderator

Re: Remove Quartz in favour of ScheduledExecutorService [message #1707794 is a reply to message #1705900]

Wed, 09 September 2015 12:04

Kai Kreuzer

Messages: 673
Registered: December 2011

Senior Member

I would agree with Dennis that we can treat Quartz as deprecated and don't build any extensions using it. Once we have new rule and persistence mechanisms that do not rely on Quartz, we can throw out this lib; until then, we will have to keep it in the stack (unless you see really a huge gain from changing the current implementations - I doubt it).

Report message to a moderator

Re: Remove Quartz in favour of ScheduledExecutorService [message #1707801 is a reply to message #1707794]

Wed, 09 September 2015 12:54

Karel Goderis

Messages: 198
Registered: March 2014

Senior Member

No, nothing to be gained in the short term as you say.

Report message to a moderator

Previous Topic:	Exporting a Binding with custom Event to OpenHAB2.
Next Topic:	Error: Could not find or load main class org.eclipse.emf.mwe2.launch.runtime.Mwe2Launcher

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Thu Apr 25 08:44:58 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter