• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Tomcat running slow with Quartz scheduler jobs

 
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi All,

We are facing performance issue with Tomcat apache 6.0, where jobs scheduled using Quartz scheduler is running very slow, jobs starting with a delay of more than 30 minutes also and navigation between the pages in the application also very slow (login to the application also). We checked the cpu utilization of the server and its nearly 100% when the jobs executes.

It was running fine for quite few days but now only we are facing this issue. Below are the server details. This is the restricted Production environment, we can't do anychanges without testing.

Tomcat version - 6.0
Tomcat Java Memory - 4.5 GB
Operating system - Windows 2008 R2 64 bit
CPU - 4
RAM size - 8 GB

Can you please guide me to resolve this performance issue.

Regards,
Gokul
 
Saloon Keeper
Posts: 27762
196
Android Eclipse IDE Tomcat Server Redhat Java Linux
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Tomcat doesn't interact with Quartz. Whatever issues you are having there are in the application, not in Tomcat.

The first step to resolving resource issues is to determine where the bottleneck is. You need to find which thread(s) are running CPU overload and what code they are executing when they do it. Although Tomcat's JMX monitoring services might help, the tools that work for general Java performance tuning also work for Tomcat-based apps.
 
Don't get me started about those stupid light bulbs.
reply
    Bookmark Topic Watch Topic
  • New Topic