Note that there are some explanatory texts on larger screens.

plurals
  1. POMuliple Websphere Application Servers attached to a single Websphere MQ Failing
    text
    copied!<p><strong>Issue:</strong> Having multiple consumer applications active specification attached to a single MQ on distributed VM servers is causing a null payload in a MQ Message. Note: See notes at the bottom. No issue with mq.</p> <p><strong>Details:</strong> I have 3 Websphere applications deployed across 2 VM servers. 1 application is a publisher and the other 2 applications are consumers attached to a single MQ Manager, and MQ. 2 consumer applications are pulling off the messages and processing them. The consumer application on the separate server receives a null payload. I have confirmed that its seems to be an issue having multiple application server instances attached to MQ. Confirmed by deploying the publisher on server 2 with consumer 2, then consumer 1 fails.</p> <p><strong>Question:</strong> Has anyone tried attaching multiple MDB applications deployed on separate server instances bind to one Queue Manager and one MQ?</p> <p><strong>Specifications:</strong></p> <p>Websphere 7, EJB 3.0 MDB's,Transactions turned off,Queue in a queue installed on another machine.</p> <p><strong>Goal:</strong></p> <p>Distributed computing, scaling up against large number of messages.</p> <p>I'm thinking this is a configuration issue but not 100% sure where to look. I had read that you could use MQLink, but I don't see why I would need to use service bus integration.</p> <p><strong>Supporting Doucmentation:</strong> [MQ Link][1</p> <p>UPDATE: I fixed the problem and it was a related to a combination of class loader issue with a duplicate classes. See Solution Notes below I added.</p> <p>EDIT HISTORY: - Clarified specifications, clarified question and added overall goal. - reference notes to solution.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload