JIRA
  1. JIRA
  2. JRA-5354

Scheduler doesnt work with subscriptions to filters on JDK 1.5

    Details

    • Type: Bug Bug
    • Status: Resolved (View Workflow)
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 3.0.3
    • Fix Version/s: 3.2 Beta
    • Component/s: Services
    • Labels:
      None
    • Environment:

      Linux kernel 2.6.6
      java 1.5.0
      resin 3.0.9
      database MSSQL server 7

      Description

      if we have subscriptions to filters the Scheduler dies with exception:

      Exception in thread "QuartzSchedulerThread" java.lang.ClassCastException: java.util.Date
      at java.sql.Timestamp.compareTo(Timestamp.java:474)
      at org.quartz.Trigger.compareTo(Trigger.java:611)
      at org.quartz.simpl.TriggerComparator.compare(RAMJobStore.java:904)
      at java.util.TreeMap.compare(TreeMap.java:1093)
      at java.util.TreeMap.getEntry(TreeMap.java:347)
      at java.util.TreeMap.remove(TreeMap.java:506)
      at java.util.TreeSet.remove(TreeSet.java:223)
      at org.quartz.simpl.RAMJobStore.acquireNextTrigger(RAMJobStore.java:735)
      at com.atlassian.scheduler.OfBizJobStore.acquireNextTrigger(OfBizJobStore.java:479)
      at org.quartz.core.QuartzSchedulerThread.run(QuartzSchedulerThread.java:197)

      and all the scheduled tasks dont execute not even services so no mails are sent and so on.
      if i remove all the subscriptions to filters everything works fine

        Issue Links

          Activity

          Hide
          Mark Chaimungkalanont [Atlassian] added a comment -

          Thanks for that. We'll try our very best to squeeze this into 3.2

          Show
          Mark Chaimungkalanont [Atlassian] added a comment - Thanks for that. We'll try our very best to squeeze this into 3.2
          Hide
          Kevin Wilson added a comment -

          To quote Tomaz: "On java 1.4.2 is working with no problems."

          Now do you mean 1.4.2_07 or _08?

          (or whichever one implemented the fix for the memory leak that chews up all the available memory over time or with heavy usage.)

          Show
          Kevin Wilson added a comment - To quote Tomaz: "On java 1.4.2 is working with no problems." Now do you mean 1.4.2_07 or _08? (or whichever one implemented the fix for the memory leak that chews up all the available memory over time or with heavy usage.)
          Hide
          Tomaz Cerar added a comment -

          I have just checked and we are using 1.4.2_06 on production server
          and on testing one 1.4.2_08 and I dont see any problems.

          Show
          Tomaz Cerar added a comment - I have just checked and we are using 1.4.2_06 on production server and on testing one 1.4.2_08 and I dont see any problems.
          Hide
          Mark Chaimungkalanont [Atlassian] added a comment -

          Quartz has now been upgraded & successfully tested in JDK 1.5

          Show
          Mark Chaimungkalanont [Atlassian] added a comment - Quartz has now been upgraded & successfully tested in JDK 1.5
          Hide
          Tomaz Cerar added a comment -

          Sun has fixed their bug in jdk... and they say it is fixed in jdk 5.0 update 7
          can you just check that it wont break any compatibily...

          Show
          Tomaz Cerar added a comment - Sun has fixed their bug in jdk... and they say it is fixed in jdk 5.0 update 7 can you just check that it wont break any compatibily...

            People

            • Assignee:
              Mark Chaimungkalanont [Atlassian]
              Reporter:
              Tomaz Cerar
            • Votes:
              10 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: