Details

    • Type: Task
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.6
    • Component/s: Development
    • Security Level: Public (Public: Anyone can view)
    • Labels:
      None
    • Sprint:
      Middleware 2.5.2 Sprint 5, Rice Sprint 2015-02-18, Rice Sprint 2015-03-04, Rice Sprint 2015-03-18, Rice Sprint 2015-04-01, Rice Sprint 2015-05-13
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required
    • Code Review Status:
      Not Required
    • Include in Release Notes?:
      Yes
    • Story Points:
      8

      Description

      Do this on trunk and we are going to attempt to identify and fix the spring 4 performance issues as noted on KULRICE-12991.

        Attachments

          Issue Links

            Activity

            Hide
            cpedersen Corey Pedersen (Inactive) added a comment -

            I have tested running the attached oracle sql against a rice-2.5 oracle 12c db. But I do not have a rice-2.5 system using oracle currently configured so could not test the results.

            Show
            cpedersen Corey Pedersen (Inactive) added a comment - I have tested running the attached oracle sql against a rice-2.5 oracle 12c db. But I do not have a rice-2.5 system using oracle currently configured so could not test the results.
            Hide
            shahess Shannon Hess added a comment - - edited

            I'm attaching an updated oracle SQL script called "KULRICE-14144_oracle_20150304 UPDATED.sql". The following line has been added to the script:

            alter table krsb_qrtz_fired_triggers add sched_time number(13) NOT NULL;
            

            The corresponding line is also in the mysql scripts, so I believe it was just left out of the oracle scripts by accident.

            After bringing in the patch, the QuartzTest and MessagingServiceTest are successful (after running either the original or the updated oracle scripts). I am only able to start up rice after running the update oracle scripts. Without the added line, there is an error thrown regarding the sched_time not being found.

            Show
            shahess Shannon Hess added a comment - - edited I'm attaching an updated oracle SQL script called " KULRICE-14144 _oracle_20150304 UPDATED.sql". The following line has been added to the script: alter table krsb_qrtz_fired_triggers add sched_time number(13) NOT NULL; The corresponding line is also in the mysql scripts, so I believe it was just left out of the oracle scripts by accident. After bringing in the patch, the QuartzTest and MessagingServiceTest are successful (after running either the original or the updated oracle scripts). I am only able to start up rice after running the update oracle scripts. Without the added line, there is an error thrown regarding the sched_time not being found.
            Hide
            cpedersen Corey Pedersen (Inactive) added a comment -

            Updated attached Oracle sql looks good. Thanks Shannon.

            Show
            cpedersen Corey Pedersen (Inactive) added a comment - Updated attached Oracle sql looks good. Thanks Shannon.
            Show
            cniesen Claus Niesen added a comment - FYI: Quartz 1.8.x to Quartz 2.0 Migration Guide
            Hide
            shahess Shannon Hess added a comment - - edited

            An error was occurring due to the removal of the sched_time column to krsb_qrtz_fired_triggers table. Claus indicated that it could be added back in since it was removed because we didn't think it was needed. (It was not referenced in http://quartz-scheduler.org/documentation/quartz-2.x/migration-guide)

            Pull request : https://github.com/kuali/rice/pull/171

            Error:

            2015-06-01 14:37:02,802 [rice.ksb.scheduler_QuartzSchedulerThread] u:/d: ERROR org.quartz.core.ErrorLogger - An error occurred while scanning for the next triggers to fire.
            org.quartz.JobPersistenceException: Couldn't acquire next trigger: ORA-00904: "SCHED_TIME": invalid identifier
             [See nested exception: java.sql.SQLException: ORA-00904: "SCHED_TIME": invalid identifier
            ]
            	at org.quartz.impl.jdbcjobstore.JobStoreSupport.acquireNextTrigger(JobStoreSupport.java:2848)
            	at org.quartz.impl.jdbcjobstore.JobStoreSupport$40.execute(JobStoreSupport.java:2759)
            	at org.quartz.impl.jdbcjobstore.JobStoreSupport$40.execute(JobStoreSupport.java:2757)
            	at org.quartz.impl.jdbcjobstore.JobStoreSupport.executeInNonManagedTXLock(JobStoreSupport.java:3787)
            	at org.quartz.impl.jdbcjobstore.JobStoreSupport.acquireNextTriggers(JobStoreSupport.java:2756)
            	at org.quartz.core.QuartzSchedulerThread.run(QuartzSchedulerThread.java:272)
            Caused by: java.sql.SQLException: ORA-00904: "SCHED_TIME": invalid identifier
            
            	at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)
            	at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:331)
            	at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:288)
            	at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:745)
            	at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:216)
            	at oracle.jdbc.driver.T4CPreparedStatement.executeForRows(T4CPreparedStatement.java:966)
            	at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1170)
            	at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3339)
            	at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:3423)
            	at org.enhydra.jdbc.core.CorePreparedStatement.executeUpdate(CorePreparedStatement.java:102)
            	at org.quartz.impl.jdbcjobstore.StdJDBCDelegate.insertFiredTrigger(StdJDBCDelegate.java:2666)
            	at org.quartz.impl.jdbcjobstore.JobStoreSupport.acquireNextTrigger(JobStoreSupport.java:2832)
            	... 5 more
            
            Show
            shahess Shannon Hess added a comment - - edited An error was occurring due to the removal of the sched_time column to krsb_qrtz_fired_triggers table. Claus indicated that it could be added back in since it was removed because we didn't think it was needed. (It was not referenced in http://quartz-scheduler.org/documentation/quartz-2.x/migration-guide ) Pull request : https://github.com/kuali/rice/pull/171 Error: 2015-06-01 14:37:02,802 [rice.ksb.scheduler_QuartzSchedulerThread] u:/d: ERROR org.quartz.core.ErrorLogger - An error occurred while scanning for the next triggers to fire. org.quartz.JobPersistenceException: Couldn't acquire next trigger: ORA-00904: "SCHED_TIME" : invalid identifier [See nested exception: java.sql.SQLException: ORA-00904: "SCHED_TIME" : invalid identifier ] at org.quartz.impl.jdbcjobstore.JobStoreSupport.acquireNextTrigger(JobStoreSupport.java:2848) at org.quartz.impl.jdbcjobstore.JobStoreSupport$40.execute(JobStoreSupport.java:2759) at org.quartz.impl.jdbcjobstore.JobStoreSupport$40.execute(JobStoreSupport.java:2757) at org.quartz.impl.jdbcjobstore.JobStoreSupport.executeInNonManagedTXLock(JobStoreSupport.java:3787) at org.quartz.impl.jdbcjobstore.JobStoreSupport.acquireNextTriggers(JobStoreSupport.java:2756) at org.quartz.core.QuartzSchedulerThread.run(QuartzSchedulerThread.java:272) Caused by: java.sql.SQLException: ORA-00904: "SCHED_TIME" : invalid identifier at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:331) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:288) at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:745) at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:216) at oracle.jdbc.driver.T4CPreparedStatement.executeForRows(T4CPreparedStatement.java:966) at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1170) at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3339) at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:3423) at org.enhydra.jdbc.core.CorePreparedStatement.executeUpdate(CorePreparedStatement.java:102) at org.quartz.impl.jdbcjobstore.StdJDBCDelegate.insertFiredTrigger(StdJDBCDelegate.java:2666) at org.quartz.impl.jdbcjobstore.JobStoreSupport.acquireNextTrigger(JobStoreSupport.java:2832) ... 5 more

              People

              • Assignee:
                shahess Shannon Hess
                Reporter:
                ewestfal Eric Westfall
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: