Update quartz from 1.6.0 to 2.x

[padcom]

From [email protected] on October 30, 2013 17:59:01

What steps will reproduce the problem? 1.login to Probe
2.enter login/password admin 3. What is the expected result? Access to Probe What happens instead? Application encountered an unexpected error :javax.servlet.ServletException: "Servlet.init()"
ERROR com.googlecode.psiprobe.ProbeServlet - Context initialization failed
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'handlerMapping' defined in ServletContext resource [/WEB-INF/spring-probe-servlet.xml]: Initialization of bean failed; nested exception is org.springframework.beans.factory.CannotLoadBeanClassException: Error loading class [org.springframework.scheduling.quartz.CronTriggerBean] for bean with name 'connectorStatsTrigger' defined in ServletContext resource [/WEB-INF/spring-probe-stats.xml]: problem with class file or dependent class; nested exception is java.lang.IncompatibleClassChangeError: class org.springframework.scheduling.quartz.CronTriggerBean has interface org.quartz.CronTrigger as super class What version of Probe are you using? 2.3.3 What environment (browser version, Tomcat version, JVM version, server OS)? Windows 7 64bits, TomEE 1.5.1 (Tomcat 7.0.34), JDK 1.7.0_11-b21, FireFox 23/IE 8. Please provide any additional information below. (Attach logs or stack traces as files instead of pasting the contents here.)

Attachment: probe.log

Original issue: http://code.google.com/p/psi-probe/issues/detail?id=379

[padcom]

From [email protected] on October 31, 2013 10:59:17

Does TomEE contain quartz already?

Status: NeedInfo

[padcom]

From [email protected] on November 04, 2013 12:47:04

Yes there is quartz-2.1.6.jar

[padcom]

From [email protected] on November 05, 2013 14:05:55

PSI Probe also contains quartz, so they are conflicting. Try removing the quartz jar from PSI Probe and see if that works.

[padcom]

From [email protected] on November 10, 2013 12:48:31

Hello.
It's not working.
The webapp is running in tomcat manager app, but when i'm going on with the
navigator i've got this error :

36 more Caused by:
org.springframework.beans.factory.CannotLoadBeanClassException: Error
loading class [org.springframework.scheduling.quartz.CronTriggerBean] for
bean with name 'connectorStatsTrigger' defined in ServletContext resource
[/WEB-INF/spring-probe-stats.xml]: problem with class file or dependent
class; nested exception is java.lang.IncompatibleClassChangeError: class
org.springframework.scheduling.quartz.CronTriggerBean has interface
org.quartz.CronTrigger as super class at

In the lib tomcat's directory i've got quartz-2.1.6.jar with the
Crontrigger class !

[padcom]

From [email protected] on November 20, 2013 13:23:05

Probe uses quartz 1.6.0. We have to update quartz for it to work.

I can't promise we will support TomEE. There are a lot of variants of Tomcat and we can't support them all. However, we'll try to get this resolved.

Summary: Update quartz from 1.6.0 to 2.x (was: Use Probe on TomEE 1.5.1)
Status: Accepted
Labels: -Type-Defect -Priority-High -Milestone-TBD Type-Enhancement Priority-Medium Milestone-2.4.0 Component-Interop

[padcom]

From [email protected] on January 28, 2014 07:26:30

@dad.depoortere: see issue 396 . I'm going to try.

[padcom]

From [email protected] on April 11, 2014 16:34:35

Labels: Stacktrace

[sirazure]

Upgrade to newest quartz is stopped by current spring version. If we want to upgrade quartz to 2.x line we need upgrade spring libraries to 3.2.x or 4.1.x line

[padcom]

It would be great to have the Spring dependencies updated to 3.x and to get
rid of the .xml configuration in favor of @RequestMapping annotation...

2014-09-10 21:24 GMT+02:00 Piotr Boryczko [email protected]:

Upgrade to newest quartz is stopped by current spring version. If we want
to upgrade quartz to 2.x line we need upgrade spring libraries to 3.2.x or
4.1.x line

—
Reply to this email directly or view it on GitHub
#379 (comment)
.