Hi all,
We are evaluating Resin as our potential app server for our large scale
J2EE application.
Environment: Resin 3.13 Pro
Quartz: 1.60
OS: Debian 4
JVM:1.5.03
Currently we are getting some trouble about Quartz and Resin, mainly
about serialization problems over Hessian protocol.
We deployed Quartz outside the container, using RMI Registry to talk
with Resin.
Firstly, we tried run Quartz jobs inside the Quartz Server by calling
remote EJB. However, seems Hessian does not like hibernate proxyed
objects and can not do serialization properly. Then we decide pass the
Quartz jobs to the container and executing jobs inside the resin to
avoid pass hibernate object over the wire.
However, this time seems Hessian can not serialize JobExecutionContext
object from quartz. The JobExecutionContext class is Serializable and I
have verified this by using standard File serialization. Seems something
funny happens in constructor in JobExecutionContext during the
serialization.
public JobExecutionContext(Scheduler scheduler,
TriggerFiredBundle firedBundle, Job job) {
this.scheduler = scheduler;
this.trigger = firedBundle.getTrigger();
this.calendar = firedBundle.getCalendar();
this.jobDetail = firedBundle.getJobDetail();
this.job = job;
this.recovering = firedBundle.isRecovering();
this.fireTime = firedBundle.getFireTime();
this.scheduledFireTime = firedBundle.getScheduledFireTime();
this.prevFireTime = firedBundle.getPrevFireTime();
this.nextFireTime = firedBundle.getNextFireTime();
this.jobDataMap = new JobDataMap();
this.jobDataMap.putAll(jobDetail.getJobDataMap());
this.jobDataMap.putAll(trigger.getJobDataMap());
}
Any thoughts, ideas, suggestion will be appreciated!
--
Will Tao
Java Developer
ICT Group
NetRegistry Pty Ltd
_______________________________________________
hessian-interest mailing list
[email protected]
http://maillist.caucho.com/mailman/listinfo/hessian-interest
