Non-persistent JMS messages don't fail-over in JBoss EAP cluster

Solution Verified - Updated -

Issue

In a clustered queue, non-persistent message was originally in JBoss Node 1 and when Node 1 is shutdown, we list the messages on Node 2 and Node 2 does not show the same message, which originally was showing up in Node 1. This does not happen for persistent messages. Is this an expected behavior or there is a fix for this issue?

Environment

JBoss Enterprise Application Platform (EAP) 5

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