Running JobRunr 7.0.0-RC.0 with MongoDB fails

[sverin]

I just startet to try out the new release candidate version of JobRunr together with MongoDB. But I can't get it to start. I created a new project with minimum dependencies.

JobRunr Version
7.0.0-RC.0

JDK Version
temurin java 21

Your SQL / NoSQL database
MongoDB 4.4.16 also tried MongoDB 6.0.14

I am using spring-boot-starter-parent version 3.2.4

<dependencies>

    <dependency>
	    <groupId>org.springframework.boot</groupId>
	    <artifactId>spring-boot-starter-web</artifactId>
	    <version>3.2.4</version>
    </dependency>
    
    <dependency>
	    <groupId>org.springframework.boot</groupId>
	    <artifactId>spring-boot-starter-data-mongodb</artifactId>
	    <version>3.2.4</version>
    </dependency>

    <dependency>
	    <groupId>org.jobrunr</groupId>
	    <artifactId>jobrunr-spring-boot-3-starter</artifactId>
	    <version>7.0.0-RC.0</version>
    </dependency>

</dependencies>

This i my application.yaml file

spring:
  data:
    mongodb:
      database: demo
      uri: mongodb://localhost:27017/?directConnection=true

org:
  jobrunr:
    database:
      database-name: demo
      type: mongodb

When I start my application it fails at startup with the following error, and I can't figure it out.

An attempt was made to call a method that does not exist. The attempt was made from the following location:

    org.jobrunr.storage.nosql.mongo.migrations.MongoMigration.collectionExists(MongoMigration.java:30)

The following method did not exist:

    'com.mongodb.client.ListCollectionNamesIterable com.mongodb.client.MongoDatabase.listCollectionNames()'

The calling method's class, org.jobrunr.storage.nosql.mongo.migrations.MongoMigration, was loaded from the following location:

    jar:file:/Users/<user>/.m2/repository/org/jobrunr/jobrunr/7.0.0-RC.0/jobrunr-7.0.0-RC.0.jar!/org/jobrunr/storage/nosql/mongo/migrations/MongoMigration.class

The called method's class, com.mongodb.client.MongoDatabase, is available from the following locations:

    jar:file:/Users/<user>/.m2/repository/org/mongodb/mongodb-driver-sync/4.11.1/mongodb-driver-sync-4.11.1.jar!/com/mongodb/client/MongoDatabase.class

The called method's class hierarchy was loaded from the following locations:

    com.mongodb.client.MongoDatabase: file:/Users/<user>/.m2/repository/org/mongodb/mongodb-driver-sync/4.11.1/mongodb-driver-sync-4.11.1.jar

But I have now other issues with mongodb. I have tried to add the exact same code as in the migration class and that works. Anyone else having issues with 7.0.0-RC.0 and MongoDB?

I uploaded the sample project here:
https://github.com/sverin/jobrunr-demo

[rdehuyss]

JobRunr 7 requires Mongo Driver 5. That's the cause of this issue.

Thanks for testing!

[sverin]

I updated the mongo drivers and now it works fine. Thank you.
Will do some more tests.

Is it documented somewhere that it requires Mongo Driver 5?

[rdehuyss]

No, we'll add it to the breaking changes section.

[sverin]

Encountered another issue when enabled the background job server. When I enable background job server and start the application I now receive this error.

org.jobrunr.JobRunrException: JobRunr encountered a problematic exception. Please create a bug report (if possible, provide the code to reproduce this and the stacktrace)
	at org.jobrunr.JobRunrException.shouldNotHappenException(JobRunrException.java:43) ~[jobrunr-7.0.0-RC.0.jar:7.0.0-RC.0]
	at org.jobrunr.server.JobHandler.run(JobHandler.java:44) ~[jobrunr-7.0.0-RC.0.jar:7.0.0-RC.0]
	at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:572) ~[na:na]
	at java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:358) ~[na:na]
	at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305) ~[na:na]
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144) ~[na:na]
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642) ~[na:na]
	at java.base/java.lang.Thread.run(Thread.java:1583) ~[na:na]
Caused by: java.lang.IndexOutOfBoundsException: Index 0 out of bounds for length 0
	at java.base/jdk.internal.util.Preconditions.outOfBounds(Preconditions.java:100) ~[na:na]
	at java.base/jdk.internal.util.Preconditions.outOfBoundsCheckIndex(Preconditions.java:106) ~[na:na]
	at java.base/jdk.internal.util.Preconditions.checkIndex(Preconditions.java:302) ~[na:na]
	at java.base/java.util.Objects.checkIndex(Objects.java:385) ~[na:na]
	at java.base/java.util.ArrayList.get(ArrayList.java:427) ~[na:na]
	at org.jobrunr.jobs.JobListVersioner.validateJobs(JobListVersioner.java:24) ~[jobrunr-7.0.0-RC.0.jar:7.0.0-RC.0]
	at org.jobrunr.jobs.JobListVersioner.areNewJobs(JobListVersioner.java:19) ~[jobrunr-7.0.0-RC.0.jar:7.0.0-RC.0]
	at org.jobrunr.storage.nosql.mongo.MongoDBStorageProvider.save(MongoDBStorageProvider.java:336) ~[jobrunr-7.0.0-RC.0.jar:7.0.0-RC.0]
	at org.jobrunr.storage.StorageProvider.getJobsToProcess(StorageProvider.java:166) ~[jobrunr-7.0.0-RC.0.jar:7.0.0-RC.0]
	at org.jobrunr.storage.ThreadSafeStorageProvider.getJobsToProcess(ThreadSafeStorageProvider.java:150) ~[jobrunr-7.0.0-RC.0.jar:7.0.0-RC.0]
	at org.jobrunr.server.tasks.steward.OnboardNewWorkTask.runTask(OnboardNewWorkTask.java:29) ~[jobrunr-7.0.0-RC.0.jar:7.0.0-RC.0]
	at org.jobrunr.server.tasks.Task.run(Task.java:43) ~[jobrunr-7.0.0-RC.0.jar:7.0.0-RC.0]
	at org.jobrunr.server.JobHandler.lambda$run$0(JobHandler.java:36) ~[jobrunr-7.0.0-RC.0.jar:7.0.0-RC.0]
	at java.base/java.util.Arrays$ArrayList.forEach(Arrays.java:4305) ~[na:na]
	at org.jobrunr.server.JobHandler.run(JobHandler.java:36) ~[jobrunr-7.0.0-RC.0.jar:7.0.0-RC.0]
	... 6 common frames omitted

This use the same sample project linked above. When I debug I can see that the size of the jobVersioners is zero (0) in the JobListVersioner class. This happens with a new database, directly at startup.

[rdehuyss]

Thank you so much, that was a missing test case. Fixed by PR #972.