Contributions
Test Case History not displaying in UI - "DataIntegrityViolationException" value too long
I have a project that will not display the Test History for the test cases in the UI. The Transaction Log displays fine. All other test projects display fine. While first test case runs the ReadyAPI Log tab shows the following error for Value too long for column "PROJECT_ID.VARCHAR(36)..." Anyone have idea what value is too long that could cause this, I am stumped.. ReadyAPI Log: 2023-02-02 08:29:50,915 ERROR [AbstractTestCaseRunner] An error occurred when notifying the listener after the test run. org.springframework.dao.DataIntegrityViolationException: PreparedStatementCallback; Value too long for column "PROJECT_ID VARCHAR(36)": "'e4bd8fh5-3048-4mjg6-8b65-07d49b0ed576' (37)"; SQL statement: INSERT INTO test_run_history (MODEL_ITEM_ID, NAME, TYPE, STARTED, DURATION, TEST_STEPS_RUN, TEST_STEPS_CONFIGURED, TEST_STEPS_FAILED, ASSERTIONS_CONFIGURED, ASSERTIONS_RUN, ASSERTIONS_FAILED, ENVIRONMENT, STOP_REASON, EXECUTION_ID, PROJECT_ID) VALUES(?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?) [22001-200]; nested exception is org.h2.jdbc.JdbcSQLDataException: Value too long for column "PROJECT_ID VARCHAR(36)": "'e4bd8fh5-3048-4mjg6-8b65-07d49b0ed576' (37)"; SQL statement: INSERT INTO test_run_history (MODEL_ITEM_ID, NAME, TYPE, STARTED, DURATION, TEST_STEPS_RUN, TEST_STEPS_CONFIGURED, TEST_STEPS_FAILED, ASSERTIONS_CONFIGURED, ASSERTIONS_RUN, ASSERTIONS_FAILED, ENVIRONMENT, STOP_REASON, EXECUTION_ID, PROJECT_ID) VALUES(?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?) [22001-200] at org.springframework.jdbc.support.SQLErrorCodeSQLExceptionTranslator.doTranslate(SQLErrorCodeSQLExceptionTranslator.java:251) ~[spring-jdbc-5.3.1.jar:5.3.1] at org.springframework.jdbc.support.AbstractFallbackSQLExceptionTranslator.translate(AbstractFallbackSQLExceptionTranslator.java:70) ~[spring-jdbc-5.3.1.jar:5.3.1] at org.springframework.jdbc.core.JdbcTemplate.translateException(JdbcTemplate.java:1541) ~[spring-jdbc-5.3.1.jar:5.3.1] at org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:667) ~[spring-jdbc-5.3.1.jar:5.3.1] at org.springframework.jdbc.core.JdbcTemplate.update(JdbcTemplate.java:991) ~[spring-jdbc-5.3.1.jar:5.3.1] at org.springframework.jdbc.core.simple.AbstractJdbcInsert.executeInsertAndReturnKeyHolderInternal(AbstractJdbcInsert.java:433) ~[spring-jdbc-5.3.1.jar:5.3.1] at org.springframework.jdbc.core.simple.AbstractJdbcInsert.executeInsertAndReturnKeyInternal(AbstractJdbcInsert.java:413) ~[spring-jdbc-5.3.1.jar:5.3.1] at org.springframework.jdbc.core.simple.AbstractJdbcInsert.doExecuteAndReturnKey(AbstractJdbcInsert.java:382) ~[spring-jdbc-5.3.1.jar:5.3.1] at org.springframework.jdbc.core.simple.SimpleJdbcInsert.executeAndReturnKey(SimpleJdbcInsert.java:132) ~[spring-jdbc-5.3.1.jar:5.3.1] at com.smartbear.ready.db.repository.jdbc.JdbcTestRunHistoryEntryRepository.add(JdbcTestRunHistoryEntryRepository.java:124) ~[ready-api-db-3.9.2.jar:?] at com.smartbear.ready.db.repository.jdbc.JdbcTestRunHistoryEntryRepository.add(JdbcTestRunHistoryEntryRepository.java:1) ~[ready-api-db-3.9.2.jar:?] at com.eviware.soapui.impl.wsdl.history.TestRunHistoryCollector.a(TestRunHistoryCollector.java:145) ~[ready-api-soapui-pro-3.9.2.jar:3.9.2] at com.eviware.soapui.impl.wsdl.history.TestRunHistoryCollector.afterRun(TestRunHistoryCollector.java:98) ~[ready-api-soapui-pro-3.9.2.jar:3.9.2] at com.eviware.soapui.impl.wsdl.support.AbstractTestCaseRunner.notifyAfterRun(AbstractTestCaseRunner.java:388) [ready-api-soapui-3.9.2.jar:3.9.2] at com.eviware.soapui.impl.wsdl.support.AbstractTestCaseRunner.internalFinally(AbstractTestCaseRunner.java:229) [ready-api-soapui-3.9.2.jar:3.9.2] at com.eviware.soapui.impl.wsdl.testcase.WsdlTestCaseRunner.internalFinally(WsdlTestCaseRunner.java:105) [ready-api-soapui-3.9.2.jar:3.9.2] at com.eviware.soapui.impl.wsdl.support.AbstractTestCaseRunner.internalFinally(AbstractTestCaseRunner.java:1) [ready-api-soapui-3.9.2.jar:3.9.2] at com.eviware.soapui.impl.wsdl.support.AbstractTestRunner.run(AbstractTestRunner.java:154) [ready-api-soapui-3.9.2.jar:3.9.2] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) [?:?] at java.util.concurrent.FutureTask.run(FutureTask.java:264) [?:?] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1130) [?:?] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:630) [?:?]226Views0likes0CommentsData Source - Data Connection SQL Query box unusable after upgrade to 3.6.0
After upgrading from Ready API 3.3 to 3.6 the SQL Query box in the DataSource step (using Data Connection) is unreadable / unusablem it only shows part of the line.4 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.1KViews0likes5Comments