HornetQ server is getting shutdown due to a Critical Error

Solution Unverified - Updated -

Issue

  • HornetQ server is running inside JBossEAP and looks like HornetQ server getting shutdown with following critical error ( though log level is WARN )
WARN  [org.hornetq.core.server] (Old I/O server worker (parentId: -882389059, [id: 0xcb67cfbd, /aaa.bbb.ccc.ddd:5445])) HQ222010: Critical IO Error, shutting down the server. file=NIOSequentialFile /exampledirectory/jms/data/paging/abc63d07e-1r3h-34e5-673b-9367b87f743c/000008263.page, message=null: HornetQException[errorType=IO_ERROR message=null]

After this error it repeatedly prints

WARN  [org.hornetq.core.server] (pool-5-thread-1) HQ224064: Queue jms.queue.HistoryQueue, on address=jms.queue.HistoryQueue, is taking too long to flush deliveries. Watch out for frozen clients.

After this HornetQ server is gone

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP)
    • 6.2
    • 6.3

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content