Skip to content
This repository has been archived by the owner on Jan 25, 2024. It is now read-only.

Error in setting org.quartz.jobStore.mongoUri in quartz.properties #41

Closed
vivganes opened this issue Nov 6, 2013 · 6 comments
Closed

Comments

@vivganes
Copy link
Contributor

vivganes commented Nov 6, 2013

I used the following quartz.properties file.

# Use the MongoDB store
org.quartz.jobStore.class=com.novemberain.quartz.mongodb.MongoDBJobStore
# MongoDB URI (optional if 'org.quartz.jobStore.addresses' is set)
org.quartz.jobStore.mongoUri=<<my Mongo URI?>>
# comma separated list of mongodb hosts/replica set seeds (optional if 'org.quartz.jobStore.mongoUri' is set)
#org.quartz.jobStore.addresses=localhost
org.quartz.jobStore.dbName=<<my db name>>
# Will be used to create collections like mycol_jobs, mycol_triggers, mycol_calendars, mycol_locks
org.quartz.jobStore.collectionPrefix=quartz
# thread count setting is ignored by the MongoDB store but Quartz requries it
org.quartz.threadPool.threadCount=10

I get the following exception during initialization of Quartz.

Stack trace:

Caused by: java.lang.NoSuchMethodException: No setter for property 'mongoUri'
at org.quartz.impl.StdSchedulerFactory.setBeanProps(StdSchedulerFactory.java:1372)
at org.quartz.impl.StdSchedulerFactory.instantiate(StdSchedulerFactory.java:848)
... 8 more

@michaelklishin
Copy link
Owner

There is a setter for mongoUri. What Quartz version do you use?

@michaelklishin
Copy link
Owner

Looking at Quartz source for 2.1.x and 2.2.0, the line that thrown an exception does not match what's in the stack trace posted.

@vivganes
Copy link
Contributor Author

vivganes commented Nov 7, 2013

I am using "org.quartz-scheduler" % "quartz" % "2.1.5"

@vivganes
Copy link
Contributor Author

vivganes commented Nov 7, 2013

@vivganes
Copy link
Contributor Author

vivganes commented Nov 7, 2013

Also, i am using "com.novemberain" % "quartz-mongodb" % "1.3.0-beta2"
with resolver
resolvers += "Clojars Repository for quartz-mongodb" at "http://clojars.org/repo",

@vivganes
Copy link
Contributor Author

vivganes commented Nov 7, 2013

I was using old and beta jars of quartz-mongodb. I changed to 1.3.0 and the error is gone :)

Closing this issue.

@vivganes vivganes closed this as completed Nov 7, 2013
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants