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))
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))
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 !!
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 !!
Anton Mazkovoi [Atlassian] added a comment - 12/Feb/06 05:28 PM Yes, I have seen several problem is IBM JDK where 'inheriting' from an interface was not properly done.
Lets explicitly put the 'implements' line in.
~Sam, please reference this issue in the comment in code to explain why the explicit implement is added.
Anton
Third-party issue
Resolved
Major
JiraSchedulerLauncher not notified with WSAD 5.1.2
Lets explicitly put the 'implements' line in.
~Sam, please reference this issue in the comment in code to explain why the explicit implement is added.
Anton