Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Couldn't acquire next trigger: Invalid column name 'SCHED_TIME'. #231

Closed
wangyw opened this issue May 20, 2018 · 2 comments
Closed

Couldn't acquire next trigger: Invalid column name 'SCHED_TIME'. #231

wangyw opened this issue May 20, 2018 · 2 comments

Comments

@wangyw
Copy link

wangyw commented May 20, 2018

I upgraded from Quartz 2.0.1 to 2.2.3, and kicked off an existing quartz job, but I ran into this exception.

2018-05-20 11:38:29,802-0700 [toe=] [] [,,] ERROR - An error occurred while scanning for the next triggers to fire. org.quartz.JobPersistenceException: Couldn't acquire next trigger: Invalid column name 'SCHED_TIME'.
	at org.quartz.impl.jdbcjobstore.JobStoreSupport.acquireNextTrigger(JobStoreSupport.java:2864) ~[quartz-2.2.3.jar:?]
	at org.quartz.impl.jdbcjobstore.JobStoreSupport$40.execute(JobStoreSupport.java:2759) ~[quartz-2.2.3.jar:?]
	at org.quartz.impl.jdbcjobstore.JobStoreSupport$40.execute(JobStoreSupport.java:2757) ~[quartz-2.2.3.jar:?]
	at org.quartz.impl.jdbcjobstore.JobStoreSupport.executeInNonManagedTXLock(JobStoreSupport.java:3803) ~[quartz-2.2.3.jar:?]
	at org.quartz.impl.jdbcjobstore.JobStoreSupport.acquireNextTriggers(JobStoreSupport.java:2756) ~[quartz-2.2.3.jar:?]
	at org.quartz.core.QuartzSchedulerThread.run(QuartzSchedulerThread.java:272) [quartz-2.2.3.jar:?]
Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Invalid column name 'SCHED_TIME'.
	at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:216) ~[sqljdbc-4.jar:?]
	at com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(SQLServerStatement.java:1515) ~[sqljdbc-4.jar:?]
	at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.doExecutePreparedStatement(SQLServerPreparedStatement.java:404) ~[sqljdbc-4.jar:?]
	at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement$PrepStmtExecCmd.doExecute(SQLServerPreparedStatement.java:350) ~[sqljdbc-4.jar:?]
	at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:5696) ~[sqljdbc-4.jar:?]
	at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:1715) ~[sqljdbc-4.jar:?]
	at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(SQLServerStatement.java:180) ~[sqljdbc-4.jar:?]
	at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(SQLServerStatement.java:155) ~[sqljdbc-4.jar:?]
	at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.executeUpdate(SQLServerPreparedStatement.java:314) ~[sqljdbc-4.jar:?]
	at com.mchange.v2.c3p0.impl.NewProxyPreparedStatement.executeUpdate(NewProxyPreparedStatement.java:105) ~[c3p0-0.9.1.1.jar:0.9.1.1]
	at org.quartz.impl.jdbcjobstore.StdJDBCDelegate.insertFiredTrigger(StdJDBCDelegate.java:2666) ~[quartz-2.2.3.jar:?]
	at org.quartz.impl.jdbcjobstore.JobStoreSupport.acquireNextTrigger(JobStoreSupport.java:2847) ~[quartz-2.2.3.jar:?]
	... 5 more
@yzumis
Copy link

yzumis commented Aug 8, 2018

You can check the following document:

http://www.quartz-scheduler.org/documentation/quartz-2.2.x/new-in-quartz-2_2.html

You will need to add a new column in the database

yasak5 added a commit to yasak5/MassTransit-Quartz that referenced this issue Aug 9, 2018
When you run this script and then run MassTransit.QuartzService, you receive "Couldn't acquire next trigger: Invalid column name 'SCHED_TIME'" error.
according to following links, we should add new column named SCHED_TIME.

quartz-scheduler/quartz#231
http://www.quartz-scheduler.org/documentation/quartz-2.2.x/new-in-quartz-2_2.html
@zemian
Copy link
Contributor

zemian commented Feb 15, 2019

Closing outdated, unresolved issues. Please, reopen if still relevant.

See https://github.com/quartz-scheduler/quartz/wiki/How-To-Submit-New-Issue

@zemian zemian closed this as completed Feb 15, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants