Messaging redundancy fails in some cases

Solution Verified - Updated -

Issue

I am trying out the redundancy using a cluster. see this scenario. Note: instances are connected using static connectors - althogh same behavior was seen using UDP broadcast. I have 2 instances primary and backup using replication.

  1. Run Instance1, Instance2
  2. Run clients - 1 producer and 1 consumer
  3. Start sending ~500 messages
  4. Stop Instance2, Instance1
  5. Run Instance2- Now the messages should be processed by the secondary Instance, but actually the system gets stack..

Viewing the log it appears that Instance2 still thinks it is backup. As long as Instance1 is down the system doesn't work.

Is this expected?

Environment

  • Red Hat JBoss Enterprise Application Platform
    • 6.x

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