Features

• issue #37 - this release adds a spring-boot-starter. This makes it even easier to get started with JobRunr in Spring
• issue #33 - JobRunr does automatic cleanup of succeeded jobs. These are now configurable

Bugfixes

• issue #38 - when enqueueing a private method, a java.lang.IllegalStateException: Unknown INVOKESPECIAL instruction was thrown. Now, a nice error message is shown

Breaking change

• issue #36 - we replaced scheduleRecurringly with scheduleRecurrently as it is grammatical more correct

Features

None

Bugfixes

#32 - Succeeded jobs are not visible

Features

Improvements in the Fluent API:

         boolean isBackgroundJobServerEnabled = true; // or get it via ENV variables
         boolean isDashboardEnabled = true; // or get it via ENV variables
         JobRunr.configure()
                .useStorageProvider(new DefaultSqlStorageProvider(da, DefaultSqlStorageProvider.DatabaseOptions.SKIP_CREATE))
                .useJobActivator(applicationContext::getBean)
                .useDefaultBackgroundJobServerIf(isBackgroundJobServerEnabled)
                .useDashboardIf(isDashboardEnabled)
                .initialize();

Bugfixes

• #32 - Succeeded jobs are not visible (Javascript error)

Features

Support for ElasticSearch

Bugfixes

#30 - Dashboard uptime sensor updating randomly
#31 - Daily jobs running more than once

Features

• Support for JDK 16 and Project Loom

Bugfixes

• Redis improvements
• MongoDB improvements
• #27
• #28

Bugfixes

• Bugfixes regarding Jedis
• Add extra Opcodes for primitives

Features

• No new features

Features

Added an InMemoryStorageProvider
DashboardWebserver can now be started and stopped. It does not start automatically anymore, except when you use the Fluent configuration.

Bugfixes

Several small bugfixes

Breaking change

You now manually need to start the DashboardWebserver if you are using the Spring configuration way.

Features

No new features added

Bugfixes

• fix for #24
• fix for RedisStorageProvider (multi threading issues)
• UI fix - statistics not always updated

Features

• JobRunr now supports DB2

Bugfixes

• Attempt to fix #25
• the IoC container (e.g. Spring or CDI) was not used when instantiating jobs which have a default constructor. It was used only when the Job had a non-default constructor with dependencies.

Notes

• Preparation is ongoing for Quarkus and GraalVM integration

Features

• Support for Quarkus

Bugfixes

• No bugfixes

Other

• No other news

Features

• Support for MicroProfile and tested on OpenLiberty
• Support for JSON-B on top of Jackson and GSON.

Bugfixes

• No bugfixes

Other

• No other news

There was an issue with the Maven POM for version 0.9.8. This has been solved. Please note that if you upgrade from v0.9.7 you still need to to drop all JobRunr related tables. For more info, see the release notes of v0.9.8.

Features

• no new features

Bugfixes

• Fix wrong BOM in Maven Central due to Gradle platform

Other

• No other news

This release is not backwards compatible when you're running a relational database. Please drop all JobRunr related tables, they will be recreated automatically afterwards.

Features

• Live updates in the dashboard
• Logging to dashboard
• Progressbar available in dashboard
• Performance improvements

Bugfixes

• See https://github.com/jobrunr/jobrunr/milestone/1?closed=1

Other

• No other news

Features

• Added option to stop JobRunr manually

Bugfixes

No new bugfixes

Other

• Prepare for release on Maven Central

JMX Integration

JobRunr now has extensive JMX integration - using JMX you can see the amount of jobs that are enqueued, are processed or have succeeded and/or failed.

Bugfixes

• The JobDetailsASMGenerator class is refactored and is all tidied up now. This fixes issue #2.
• We also bumped into a JDK bug (JDK Bug 8193878) on Mac OS. A workaround has been implemented.

Support for extra databases

I'm glad to announce that JobRunr now supports the top 5 of all databases used in the world (according to https://db-engines.com/), including Oracle, MySQL, Microsoft SQL Server, PostgreSQL and MongoDB! On top of that, JobRunr also supports MariaDB, Redis, H2 and SQLite. Of course we have extensive tests to cover all these databases.

Easier IoC integration

At start, I designed JobRunr so that background methods using IoC injection, needed to use the following syntax:
BackgroundJob.<MyService>enqueue(x -> x.doWork()); With feedback from @plosson, I revisited this decision and one can now also use an IoC container as follows: BackgroundJob.enqueue(() -> myService.doWork()); where myService is an available instance of your service.

Bugfixes

• #7: when scheduling a Job method that was defined in an interface, JobRunr did not find the correct method. This has been solved.

Bugfixes

• The dashboard had a bug when showing overall memory consumption when there was more than 1 background job server

Other

• All dependencies were updated to their latest version
• The StorageProviderTest class is moved to the testFixtures source set to ease development for 3th-party StorageProviders

Datasource/Connection polling

In this release we added support for a lot of connection pools:

• Hikari
• C3p0
• Apache DBCP2
• Tomcat Connection pooling

GCP Cloud Sql support

In this release we also added support for Google Cloudsql

UI improvements:

• succeeded & failed jobs table is ordered desc
• on sidebar left click, jobs table is refreshed

Server improvements

• jobs are processed immediately when queue is empty

New features

• Support for method references - a background job can now be enqueued as follows: BackgroundJob.enqueue(Service::myJobToRun)
• Support for H2 databases

Bugfixes

• dashboard figures were not always shown
• Cron.weekly(Sunday) returned an exception
• Job names where not correctly shown for Jobs that got enqueued by a Recurring Job