> From: Xavier Vercoutere [mailto:xavier.vercout...@korfina.be]
> Subject: tomcat 5.5 -> tomcat 6.0
> 
> Everything is functioning perfectly except for the built-in scheduling.

What built-in scheduling is that?  One of your webapps?

It's a custom sync job ran by the quartz scheduler 

> I have to restart the Tmocat 6.0 service almost every 2 days to keep
> the schedule going.  I never head this problem with Tomcat 5.5.

What starts the scheduled job?  Have you looked in the Tomcat logs?  Have you 
taken a thread dump to see if whatever is supposed to start the scheduled job 
is running?

That is just the problem :
The scheduled job runs fine a couple of time and than at a certain moment the 
scheduled jobs is no longer executed.
I did not find any specific job related error info in the logs. I'm not a 
tomcat specialist. I've attached the log files in a rar file.
The name of the job is : dataswitchsynchronizationjob

> That leads me to the conclusion that the reason for the 'hanging' has
> to come form Tomcat itself.

"It's always somebody else's fault..."
Indeed when you First analyzed your own apps

 - Chuck


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY 
MATERIAL and is thus for use only by the intended recipient. If you received 
this in error, please contact the sender and delete the e-mail and its 
attachments from all computers.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

ÿþSymantec Mail Security replaced 
tempftp.rar with this text message.  
The original file was unscannable and 
was quarantined.



ID:MAILSERVER::SYQ9c89d881

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Reply via email to