JBoss processExpiresFrequency is not consistent

Solution Verified - Updated -

Issue

  • context.xml is configured to invalidate expired sessions every 20 minutes:
    <Manager pathname="" processExpiresFrequency="120" />
  • Real frequencies are not exactly 10 minutes. A second or several seconds are added sometimes between intervals. For example, :
    2009-12-14 04:09:54,370 DEBUG [org.apache.catalina.session.ManagerBase] Start expire sessions StandardManager at 1260760194370 sessioncount 120
2009-12-14 04:09:54,385 DEBUG [org.apache.catalina.session.ManagerBase] End expire sessions StandardManager processingTime 15 expired sessions: 10
...
2009-12-14 09:50:06,468 DEBUG [org.apache.catalina.session.ManagerBase] Start expire sessions StandardManager at 1260780606467 sessioncount 425
2009-12-14 09:50:06,497 DEBUG [org.apache.catalina.session.ManagerBase] End expire sessions StandardManager processingTime 30 expired sessions: 24

Environment

  • JBoss Application Server (AS) 4.0.5

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.