You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Xavier Vercoutere <xa...@korfina.be> on 2009/12/16 16:02:59 UTC

tomcat 5.5 -> tomcat 6.0

Hi,

 

I recently migrated  from tomcat 5.5 on a Windows 2003 server to tomcat 6.0 on a Windows 2008 server.

Everything is functioning perfectly except for the built-in scheduling.

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.

When I run the scheduled job manually at a time when the scheduling is not working any more, the job functions without any problem.

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

 

Please advice

 

Met vriendelijke groeten

Xavier Vercoutere

Tel Dir : +32 56 /52 87 22

Tel Alg  +32 56 /21 61 82

Fax : +32 56 /52.87.35

xavier.vercoutere@korfina.be 

Minister Liebaertlaan 10

B-8500 Kortrijk

 

 

 

P Denk aan het milieu vooraleer je dit bericht of de bijlagen uitprint

 

De verzending van huidig e-mailbericht gebeurt onder alle voorbehoud en zonder enige nadelige erkentenis. De informatie in dit e-mailbericht en bijlagen is strikt vertrouwelijk. Indien u niet de bedoelde ontvanger bent, gelieve dan dit bericht te vernietigen en alle kopies opgeslagen in uw systemen te wissen en de zender hiervan onmiddellijk op de hoogte te brengen. U mag dit bericht niet bewaren, kopiëren of voor om het even welk doeleinde gebruiken.  U mag evenmin de volledige inhoud of een deel ervan aan een derde bekendmaken.

 

Ce courriel vous est envoyé sous réserve de nos droits et sans aucune reconnaissance préjudiciable. L'information reprise dans ce message e-mail ainsi que dans ses annexes est strictement confidentielle. Si vous n'êtes pas le destinataire visé, veuillez détruire le présent message ainsi que toutes les copies mémorisées dans vos systèmes et en informer immédiatement l'expéditeur. Il vous est interdit de mémoriser, de copier ou d'utiliser ce message a n'importe quelle fin. Il vous est également interdit de révéler son contenu entier ou une partie de son contenu a un tiers.

 

This email is sent subject to all reservations and without prejudice to any of our rights. The information in this email and in any attachments is confidential and may be privileged. If you are not the intended recipient, please destroy this message, delete any copies held on your systems and notify the sender immediately. You should not retain, copy or use this email for any purpose, nor disclose all or any part of its content to any other person.

 


RE: tomcat 5.5 -> tomcat 6.0

Posted by "Caldarale, Charles R" <Ch...@unisys.com>.
> From: Xavier Vercoutere [mailto:xavier.vercoutere@korfina.be]
> Subject: RE: tomcat 5.5 -> tomcat 6.0
> 
> I've attached the log files in a rar file.

Attachments usually don't make it through (something stripped this one), and please never use .rar format for compression (it conflicts with standard Java EE Resource Adapter files), beside being proprietary.

 - 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-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


RE: tomcat 5.5 -> tomcat 6.0

Posted by Xavier Vercoutere <xa...@korfina.be>.
> From: Xavier Vercoutere [mailto:xavier.vercoutere@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-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


RE: tomcat 5.5 -> tomcat 6.0

Posted by "Caldarale, Charles R" <Ch...@unisys.com>.
> From: Xavier Vercoutere [mailto:xavier.vercoutere@korfina.be]
> Subject: RE: tomcat 5.5 -> tomcat 6.0
> 
> What is the preferred method for attachments ?

None.

But back to your real problem: none of the things you described are related to Tomcat, since there's no built-in scheduling facility.  You'll need to add logging statements to the scheduler to make sure it's really trying to start up the target procedure at the appropriate times, and also put some logging in the target to see if it's ever getting control.  You could use JConsole or similar monitoring mechanism to make sure the quartz thread is still alive, or if it's stuck somewhere.

 - 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-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


RE: tomcat 5.5 -> tomcat 6.0

Posted by Xavier Vercoutere <xa...@korfina.be>.
Hi

What is the preferred method for attachments ?


-----Original Message-----
From: Caldarale, Charles R [mailto:Chuck.Caldarale@unisys.com] 
Sent: woensdag 16 december 2009 16:11
To: Tomcat Users List
Subject: RE: tomcat 5.5 -> tomcat 6.0

> From: Xavier Vercoutere [mailto:xavier.vercoutere@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?

> 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 leads me to the conclusion that the reason for the 'hanging' has
> to come form Tomcat itself.

"It's always somebody else's fault..."

 - 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-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


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


RE: tomcat 5.5 -> tomcat 6.0

Posted by "Caldarale, Charles R" <Ch...@unisys.com>.
> From: Xavier Vercoutere [mailto:xavier.vercoutere@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?

> 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 leads me to the conclusion that the reason for the 'hanging' has
> to come form Tomcat itself.

"It's always somebody else's fault..."

 - 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-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org