ibm-mq

We have one MQ Queue which receives messages from an external system out of our control. Our system processing the incoming messages is a critical one and needs to be up and running 27x7 no matter what. The order in which the incoming messages are processed is also not negotiable which means we need to process them in exactly the order they arrived. To make sure our system is 100% available we deployed our system to a bunch of physical machines able to process those messages. Once the messages reached our system we put in place a mechanism to make sure the messages processing does not go out

I have a MDB which listens to WebSphere MQ. It does not picks up the messages in the order that has been received by the Queue. How can i make it read it in that order? Is it possible? Should i not use a MDB. In general, WMQ delivers messages in the order that they were received. However, several things can impact that... If the queue is set to priority instead of FIFO delivery and messages arrive in different priorities, they will be delivered "out of order". Distinguish between order produced and order delivered. If the messages are produced on a remote QMgr and there are multiple paths to

I am trying to connect to IBM Websphere MQ Server from IBM Websphere Application Server. I am getting the following error: MQJMS2013: invalid security authentication supplied for MQQueueManager What I understand is, this is because of invalid security credentials by WAS while connecting to MQ Manager. I have tried different combination of providing the MQ admin password e.g. Provide J2C authentication to MQ Connection Factory. Provide MQ admin username and password to Queues. Providing Blank username. Combination of all three above. Also, as mentioned in some of the posts, I have tried the

I have a requirement that I need to process JMS Messages (via MDB) in a way that Messages belonging to a certain group (a group ID is set) are consumed by the same bean instance. The behaviour I require in this is that Messages with the same group ID are processed sequentially (though message ordering is irrelevant), and tying them to the same MDB-instance should provide that. The messages do not carry any kind of sequence number (as it is irrelevant) and we do not know what the first or last message in a group is (there could theoratically "never" be a last message in a group). We want them