Uploaded image for project: 'jBPM'
  1. jBPM
  2. JBPM-5306

"InvalidClassException" error after upgrading from BPMS 6.0.3 to 6.1.0

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Blocker
    • None
    • None
    • Runtime Engine
    • None
    • NEW
    • NEW

    Description

      After upgrading from BPMS 6.0.3 to 6.1.0 and using quartz to store jobs, an InvalidClassException is thrown due to a class (SelfRemovalJobContext) that has been serialized and stored in DB quartz tables in 6.0.3. So now after upgrading to 6.1, it seems like it is no longer compatible with the new class.

      10:21:54,185 ERROR [org.quartz.impl.jdbcjobstore.JobStoreCMT] (QuartzScheduler_jBPMClusteredScheduler-lnx-jbpmcert.bci.cl1462971711770_MisfireHandler) MisfireHandler: Error handling misfires: Couldn't store trigger '9005-102689-73_trigger' for '9005-102689-73' job:org.drools.core.time.SelfRemovalJobContext; local class incompatible: stream classdesc serialVersionUID = 4974155438759730703, local class serialVersionUID = 614425985040796356: org.quartz.JobPersistenceException: Couldn't store trigger '9005-102689-73_trigger' for '9005-102689-73' job:org.drools.core.time.SelfRemovalJobContext; local class incompatible: stream classdesc serialVersionUID = 4974155438759730703, local class serialVersionUID = 614425985040796356 [See nested exception: java.io.InvalidClassException: org.drools.core.time.SelfRemovalJobContext; local class incompatible: stream classdesc serialVersionUID = 4974155438759730703, local class serialVersionUID = 614425985040796356]

      The root cause is due to:

      Caused by: java.io.InvalidClassException: org.drools.core.time.SelfRemovalJobContext; local class incompatible: stream classdesc serialVersionUID = 4974155438759730703, local class serialVersionUID = 614425985040796356

      At first, I thought it could be related to something db as they have upgraded that by using the available scripts for upgrading, but they should not impact quartz tables.

      So it seems like this class was stored in database by using a specific serialVersionUID (4974155438759730703) that refers to 6.0.3. However, it is not now able to retrieve that as it has been changed.

      Attachments

        Issue Links

          Activity

            People

              swiderski.maciej Maciej Swiderski (Inactive)
              swiderski.maciej Maciej Swiderski (Inactive)
              Tomáš Livora Tomáš Livora (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: