Build: #28 failed
Job: Default Job failed
Should fail if the entity already has an item in the error queue: Test case result
The below summarizes the result of the test "Should fail if the entity already has an item in the error queue" in build 28 of openmrs-eip - openmrs-eip - Default Job.
- Description
- Should fail if the entity already has an item in the error queue
- Test class
- org.openmrs.eip.mysql.watcher.route.DbEventListenerRouteTest
- Method
- shouldFailIfTheEntityAlreadyHasAnItemInTheErrorQueue
- Duration
- < 1 sec
- Status
- Failed (New Failure)
Error Log
org.springframework.jdbc.datasource.init.ScriptStatementFailedException: Failed to execute SQL script statement #1 of class path resource [sender_retry_queue.sql]: INSERT INTO sender_retry_queue (table_name, primary_key_id, operation, destination, attempt_count, snapshot, date_created) VALUES ('person', '1', 'c', 'direct:db-sync', 1, 0, '2020-02-27 00:00:00'), ('person', '1', 'u', 'direct:db-sync', 1, 0, '2020-02-27 00:00:00'), ('person', '2', 'c', 'direct:invalid-dest', 1, 0, '2020-02-27 00:00:00'), ('person', '1', 'c', 'direct:senaite', 1, 0, '2020-02-27 00:00:00'); nested exception is org.h2.jdbc.JdbcSQLSyntaxErrorException: Table "SENDER_RETRY_QUEUE" not found; SQL statement:
INSERT INTO sender_retry_queue (table_name, primary_key_id, operation, destination, attempt_count, snapshot, date_created) VALUES ('person', '1', 'c', 'direct:db-sync', 1, 0, '2020-02-27 00:00:00'), ('person', '1', 'u', 'direct:db-sync', 1, 0, '2020-02-27 00:00:00'), ('person', '2', 'c', 'direct:invalid-dest', 1, 0, '2020-02-27 00:00:00'), ('person', '1', 'c', 'direct:senaite', 1, 0, '2020-02-27 00:00:00') [42102-200]
org.springframework.jdbc.datasource.init.ScriptStatementFailedException:
Failed to execute SQL script statement #1 of class path resource [sender_retry_queue.sql]: INSERT INTO sender_retry_queue (table_name, primary_key_id, operation, destination, attempt_count, snapshot, date_created) VALUES ('person', '1', 'c', 'direct:db-sync', 1, 0, '2020-02-27 00:00:00'), ('person', '1', 'u', 'direct:db-sync', 1, 0, '2020-02-27 00:00:00'), ('person', '2', 'c', 'direct:invalid-dest', 1, 0, '2020-02-27 00:00:00'), ('person', '1', 'c', 'direct:senaite', 1, 0, '2020-02-27 00:00:00'); nested exception is org.h2.jdbc.JdbcSQLSyntaxErrorException: Table "SENDER_RETRY_QUEUE" not found; SQL statement:
INSERT INTO sender_retry_queue (table_name, primary_key_id, operation, destination, attempt_count, snapshot, date_created) VALUES ('person', '1', 'c', 'direct:db-sync', 1, 0, '2020-02-27 00:00:00'), ('person', '1', 'u', 'direct:db-sync', 1, 0, '2020-02-27 00:00:00'), ('person', '2', 'c', 'direct:invalid-dest', 1, 0, '2020-02-27 00:00:00'), ('person', '1', 'c', 'direct:senaite', 1, 0, '2020-02-27 00:00:00') [42102-200]
Caused by: org.h2.jdbc.JdbcSQLSyntaxErrorException:
Table "SENDER_RETRY_QUEUE" not found; SQL statement:
INSERT INTO sender_retry_queue (table_name, primary_key_id, operation, destination, attempt_count, snapshot, date_created) VALUES ('person', '1', 'c', 'direct:db-sync', 1, 0, '2020-02-27 00:00:00'), ('person', '1', 'u', 'direct:db-sync', 1, 0, '2020-02-27 00:00:00'), ('person', '2', 'c', 'direct:invalid-dest', 1, 0, '2020-02-27 00:00:00'), ('person', '1', 'c', 'direct:senaite', 1, 0, '2020-02-27 00:00:00') [42102-200]