Details

    • Type: Task Task
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.6
    • Component/s: Development
    • Security Level: Public (Public: Anyone can view)
    • Labels:
      None
    • Similar issues:
      KULRICE-12879Pom.xml file cleanup from Spring 4 upgrade
      KULRICE-11635Analyze upgrade to Spring 4.x
      KULRICE-12947IT Failure 4 failures with Could not start Quartz Scheduler
      KULRICE-2294Combine Rice Spring Contexts into a single Spring context
      KULRICE-6724Override Spring class to improve startup performance
      KULRICE-12995Rice Spring Configuration issues
      KULRICE-3211Upgrade to Spring 3.0.1
      KULRICE-10888Provide Rice wrapper for Spring multipart flle
      KULRICE-6306Upgrade Spring version to 3.1.0.RELEASE
      KULRICE-8244Convert delivered Rice portal from Struts to Spring
    • 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.

      1. KULRICE-14144__20150205.patch
        50 kB
        Corey Pedersen
      2. KULRICE-14144_mysql_workbench.sql
        5 kB
        Corey Pedersen
      3. KULRICE-14144_oracle_20150304.sql
        6 kB
        Corey Pedersen
      4. KULRICE-14144_oracle_20150304 UPDATED.sql
        6 kB
        Shannon Hess

        Issue Links

          Activity

          Hide
          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
          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
          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
          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
          Corey Pedersen (Inactive) added a comment -

          Updated attached Oracle sql looks good. Thanks Shannon.

          Show
          Corey Pedersen (Inactive) added a comment - Updated attached Oracle sql looks good. Thanks Shannon.
          Show
          Claus Niesen added a comment - FYI: Quartz 1.8.x to Quartz 2.0 Migration Guide
          Hide
          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
          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:
              Shannon Hess
              Reporter:
              Eric Westfall
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Agile

                  Structure Helper Panel