IDM node not starting: HQ224000: Failure in initialisation: java.nio.BufferUnderflowException
search cancel

IDM node not starting: HQ224000: Failure in initialisation: java.nio.BufferUnderflowException

book

Article ID: 197550

calendar_today

Updated On:

Products

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

Issue/Introduction

We are having an issue in one of the IDM nodes and are unable to start it.

Server log shows the following:

02:33:45,515 ERROR [org.hornetq.core.server] (MSC service thread 1-7) HQ224000: Failure in initialisation: java.nio.BufferUnderflowException
    at java.nio.Buffer.nextGetIndex(Buffer.java:498) [rt.jar:1.7.0_45]
    at java.nio.HeapByteBuffer.getInt(HeapByteBuffer.java:355) [rt.jar:1.7.0_45]
    at org.hornetq.core.journal.impl.JournalImpl.readFileHeader(JournalImpl.java:2666) [hornetq-journal-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2]
    at org.hornetq.core.journal.impl.JournalImpl.orderFiles(JournalImpl.java:384) [hornetq-journal-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2]
    at org.hornetq.core.journal.impl.JournalImpl.load(JournalImpl.java:1728) [hornetq-journal-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2]
    at org.hornetq.core.journal.impl.JournalImpl.load(JournalImpl.java:1322) [hornetq-journal-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2]
    at org.hornetq.core.journal.impl.JournalImpl.load(JournalImpl.java:1306) [hornetq-journal-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2]
    at org.hornetq.core.persistence.impl.journal.JournalStorageManager.loadMessageJournal(JournalStorageManager.java:1530) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2]
    at org.hornetq.core.server.impl.HornetQServerImpl.loadJournals(HornetQServerImpl.java:1732) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2]...

 

Cause

The HQ224000:...BufferUnderflow error indicates corruption in the JMS queue.

Resolution

The HQ224000:...BufferUnderflow error indicates corruption in the JMS queue.

The resolution is to delete the JMS queue on the affected node.

On vAPP run:

     >deleteIDMJMSqueue

On standalone Identity Manager:

Delete the Wildfly or JBoss /data directory and restart the server.

No data will be lost because IDM will read in-progress tasks back into JMS upon restart.

Additional Information

See also, RedHat solution (Requires RH login account):

https://access.redhat.com/solutions/2160491