High CPU due to rapid looping in TransactionReaper.check

Solution Verified - Updated -

Issue

  • We're seeing increased CPU on our JBoss server, leading to performance degradation and unresponsiveness.
  • Thread dumps and CPU data indicates the high CPU consumer is a Timer RepearThread, apparently stuck in TransactionReaper.check().

  • We are seeing our log fill up rapidly with messages like the following:

    DEBUG [com.arjuna.ats.arjuna.logging.arjLogger] (Thread-16) TransactionReaper::check ()
DEBUG [com.arjuna.ats.arjuna.logging.arjLoggerI18N] (Thread-16) [com.arjuna.ats.arjuna.coordinator.TransactionReaper_2] - TransactionReaper::check - comparing 1323173300843

Environment

  • JBoss Enterprise Application Platform (EAP)
    • 5.1.0 and earlier

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.