Jobrunr Jobrunr Versions Save

Celebration time!

I'm pleased to announce the release of JobRunr v6.3.0 (which is now available via Maven Central) and JobRunr Pro v6.3.0 which is available for customers with a subscription.

Since the 6.2.0 release, we did some performance improvements related to the dashboard resulting in less calls to the JobRunr rest API and we also did stability improvements which should result in less SevereJobRunrExceptions. This release adds support for Micronaut 4 and Kotlin 1.9.

In JobRunr Pro, we added Observability support, added the option to set a Job time-out, users can now sort the jobs in the dashboard and we improved the RetryPolicy which now also allows to specify a custom amount of retries per Exception. And last but not least, all dependencies were also updated.

I also want to shoutout to Sergi Almar who improved the spring-boot-starter and Geir Sagberg who fixed a bug in the dashboard for their contributions. You have my eternal 🙏.

Observability

Although the JobRunr Pro Dashboard gives instant insights how your jobs are doing, you may already have an observability platform like Jaeger, HoneyComb or New Relic running inside your organization. JobRunr Pro now out-of-the box integrates with many of these observability platforms so you can keep on top of things. This means you can now see how long your different Job instances take and where a job spends the most time right from your existing observability platform.

Job Timeout

A Job time-out is exactly what you think it is - specify it when creating a Job and if the Job is processing longer than the given time-out, JobRunr will automatically interrupt it.

Improvements

• JobRunr Pro issue 15 : [FEATURE] Job Timeout
• JobRunr Pro issue 156 : [Improvement] Pause all job processing is respected when new BackgroundJobServers start.

Bugfixes

• JobRunr issue 779: [BUG] Support for Java Records to the JacksonJsonMapper
• JobRunr issue 782: [BUG] ElectStateFilter and ApplyStateFilter are also invoked when no statechange happened.
• JobRunr issue 881: [BUG] Severe JobRunr Exception
• JobRunr Pro issue 114 : [BUG] Custom DataSource for migrations is not working
• JobRunr Pro issue 140 : [BUG] IllegalJobStateChangeException followed by SevereJobRunrException

New features

None

Bugfixes

• #796 Fix requeue and delete from dashboard

New features

None

Bugfixes

• #782 : Job State Change Filters are also invoked when no state change happened
• Improve caching of job analysis when using Java Stream API

New Features

None

Bugfixes

• jobrunr/jobrunr#777: Fix bug related to Quarkus 3.0 compatibility if using JSONB.
• jobrunr/jobrunr#779: Fix issue records not working when using Jackson

Other

All dependencies have been updated to their latest version.

Celebration time!

I'm pleased to announce the release of JobRunr v6.2.0 (which is now available via Maven Central) and JobRunr Pro v6.2.0 which is available for customers with a subscription.

This release includes an important bugfix for people running JobRunr on Windows machines that was reported by the community and a Pro customer. Sometimes, no jobs were processed on Windows due to a deadlock when querying CPU information. This has now been solved.

On top of that, we did some profiling and made JobRunr a bit faster. Last but not least, we upgraded our dependencies including Spring Boot 3 and we now also support Quarkus 3.0. Support for Quarkus 2.0 and Kotlin 1.6 has dropped as we want to stay up-to-date with the latest technologies.

For JobRunr Pro customers, we added a very cool and much requested feature: dynamic queues or load-balancing!

This means your application can now support multiple tenants concurrently. Even in a scenario where one tenant, say Tenant-A, generates millions of jobs while others only create a few, these other tenants won't be left waiting until all of Tenant-A's jobs are completed. Instead, JobRunr utilizes a round-robin load-balancing strategy to ensure each tenant receives balanced job processing, facilitating fairness in processing their jobs.

Read all about [dynamic queues]({{< ref "documentation/pro/dynamic-queues.md" >}}) in the JobRunr Pro documentation!

Improvements

• JobRunr Pro issue 28 : [FEATURE] Weighted queues
• JobRunr Pro issue 85 : [FEATURE] Fair usage / round robin job enqueueing for multi-tenant applications
• JobRunr PR v6.2 Update all dependencies and add support for Quarkus 3.

Bugfixes

• JobRunr issue 740: [BUG] Windows only - All my workers are stuck querying the ProcessCpuLoad
• JobRunr Pro issue 124: [BUG] Windows only - Enqueued jobs are not getting processed (same as JobRunr issue 740)

New Features

• jobrunr/jobrunr#751: Better JavaDoc for StorageProvider API

Bugfixes

• jobrunr/jobrunr#732: StorageProvider.recurringJobExists() returns different results depending on database
• jobrunr/jobrunr#746: Using multiple Datasources in Spring Boot is not working
• jobrunr/jobrunr#747: DocumentDB is not working as of JobRunr v6.x.x due to incompatible index

New features

None

Bugfixes

• Issue jobrunr/jobrunr-pro 113: Allow to disable high number of calls to jobrunr_job_stats view (Allow to disable JMX for JobStats)

New features

None

Bugfixes

• Fix #717 / #317 / #677 JobRunr fails to update metadata, and eventually shuts down, when using MySQL with useServerPrepStmts = true
• Fix #723 Quarkus Configuration Database Type not working

New features

None

Bugfixes

• jobrunr/jobrunr#714: Bugfix regarding migration Recurring Jobs from v5 to v6 for labels (only in OSS version)
• jobrunr/jobrunr#711: Bugfix regarding migration from Jobs from v5 to v6 for labels when using Yasson

🎉 We're happy to announce the release of JobRunr and JobRunr Pro 6.1.0 🎉.

This release includes an important bugfix that surfaced during our internal load testing that exists already since JobRunr 1.0. In some cases, JobRunr does not close an InputStream resulting in a FileSystemException because of too many open files. See GitHub issue 707 for more info.

Another big improvement is that you now have more options in the JobServerFilter, allowing you to take custom actions when a Job failed and all the retries are exhausted.

Improvements

• GitHub issue 639 : You can now change the Recurring Job schedule from the dashboard
• GitHub issue 571 : Liquibase and Flyway support
• GitHub issue 687 : Allow to have different user for SQL migrations then at runtime
• GitHub issue 671: Allow easier mocking of JobContext: you can now call MockJobContext.setUpJobContext(jobContext) which helps to test Jobs using the JobRequest & JobRequestHandler
• GitHub issue 690: Quarkus extension support for AWS DocumentDB: JobRunr now also supports AWS DocumentDB out of the box
• GitHub issue 696: The functionality of the JobServerFilter has improved a lot. You can now have custom logic that will be executed when a job succeeds, fails or fails after all retries are exhausted.

Bugfixes

• GitHub issue 50 : Performance improvements related to batch jobs
• GitHub issue 27 : Performance improvements related to batch jobs
• GitHub issue 104 : On intermittent database problems, JobRunr stops processing
• The dashboard running in Spring did not support context path
• GitHub issue 707: Classpath InputStream not closed when analysing a lambda
• GitHub issue 691: JobContext as parameter for Recurring Job not working for Quarkus (we had to work around a bug in Quarkus)
• GitHub issue 694: Primitive Parameters used in lambda are cached in some cases.