Uploaded image for project: 'Jira Server and Data Center'
  1. Jira Server and Data Center
  2. JRASERVER-9186

JiraSchedulerLauncher not notified with WSAD 5.1.2

    XMLWordPrintable

Details

    • Suggestion
    • Status: Closed (View Workflow)
    • Resolution: Fixed
    • 3.5.2
    • None
    • WSAD 5.1.2
      JDBK IBM of WTE 5.1
      java version "1.4.1"
      Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1)
      Classic VM (build 1.4.1, J2RE 1.4.1 IBM Windows 32 build cn1411-20031011 (JIT enabled: jitc))
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

    Description

      It appears that, there is a bug with com.atlassian.jira.scheduler.JiraSchedulerLauncher under WSAD/WTE 5.1.

      Developping a Service in order tio have a Rol lOver Backup, it appears that it never start with WSAD, but was correctly started when deployed on WebSphere 5.0.2.0 and WebSphere 6.0.2.0.

      JiraSchedulerLauncher was never not notified when Context was initialized. There was no ClassLoaderError and nothing other mentionned errors.

      Concerned Classes are

      public class SchedulerLauncher implements ServletContextListener {
      ...
      }
      
      public class JiraSchedulerLauncher extends SchedulerLauncher {
      ...
      }
      

      In one of my plugin, I extend JiraSchedulerLauncher as follow and replace it in web.xml

      public class JiraAddOnSchedulerLauncher extends JiraSchedulerLauncher implements javax.servlet.ServletContextListener {
      ...
      }
      

      and strangely, the Launcher is now correclty notified.

      It appears that Listener Classes have to implement explicitely the ServletContextListener interface.

      Thanks Big Blue !!

      Attachments

        Activity

          People

            Unassigned Unassigned
            5d77aaa81033 Vincent Thoulé
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: