JBoss Application Server Failure: java.io.EOFException and HornetQ Persistence Provider Errors

Products

• CA Identity Manager
• CA Identity Governance
• CA Identity Portal
• CA Identity Suite

Issue/Introduction

The JBoss application server logs report a java.io.EOFException during startup or task processing. This error typically occurs when the persistence provider (HornetQ) fails to fetch objects by ID due to underlying data corruption in the application server's temporary storage or data directories.

 

Error messages stating: 

ERROR [ims.tmt.persistence] (Thread-15 (HornetQ-client-global-threads-21606282)) PersistenceProvider: JMS:ID:7a915ca0-f81f-XXXX-XXXX-1f9a5334a1de: fetchObjectById: tried '3' times, exception getting object by id: 4d5807d3-44270f0b-XXXXXXX-c523322: java.io.EOFException

Environment

Identity Manager 14.x (Standalone / Virtual Appliance)

Cause

The error is caused by corrupt data files stored in the JBoss operational directories. This prevents the server from deserializing objects required for task persistence and messaging.

Resolution

For On-Premise Installations

Instructions must be performed while the JBoss Application Server is stopped.

1. Stop the JBoss Application Server service.
2. Navigate to the JBoss installation directory.
3. Archive and clear (or delete) all files within the following directories on all JBoss instances:
   • \standalone\tmp
   • \standalone\data
   • \standalone\log
   • Note: Ensure you move the data to a backup location before clearing.
4. Restart the JBoss Application Server.
   
   

For Virtual Appliance (vApp) Installations

Users on the Virtual Appliance may encounter permission restrictions when attempting to manually clear the directories listed above.

1. Use the following alias to clear the JMS queue data:
   

   deleteIDMJMSqueue

2. Restart the Identity Manager services via the vApp console.

Additional Information

Application Server must be off in order to archive the corrupt data.