Problem Statement:
The Adeptia Connect EventScheduler fails to execute scheduled trigger operations due to SQL syntax errors during database queries. These errors, caused by incorrect SQL generation, prevent the system from acquiring the next scheduled trigger. Additionally, event activation fails when the event is already marked as active, indicating issues with event state management.
Issue Description:
The EventScheduler service in Adeptia Connect encounters a JobPersistenceException while scanning for the next triggers due to an SQL syntax error:
"You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '1 TRIGGER_NAME, TRIGGER_GROUP, NEXT_FIRE_TIME, PRIORITY FROM ABPM_TRIGGERS...'"
Additionally, database event activation fails with the following message:
"Error in activating Database Event \"WC_DE_SQLServerEvent(...)\": Event is already activated."
These issues are causing disruptions in scheduled event execution and event lifecycle management.
Suggested Solution:
To resolve the issue, modify the value of the QUARTZ_DRIVER_DELEGATE_CLASS property in the Event microservices within the environment.
Old value: org.quartz.impl.jdbcjobstore.MSSQLDelegate
New value: org.quartz.impl.jdbcjobstore.StdJDBCDelegate
For other databases, use the following values:
Database | Value | Description |
Azure SQL | org.quartz.impl.jdbcjobstore.MSSQLDelegate | SQL Server delegate for Azure SQL |
Oracle | org.quartz.impl.jdbcjobstore.oracle.OracleDelegate | Oracle database delegate |
Azure MySQL | org.quartz.impl.jdbcjobstore.StdJDBCDelegate | Standard JDBC delegate for MySQL |
This solution addresses the SQL syntax errors and improves event trigger handling.
Comments
0 comments
Please sign in to leave a comment.