C2180-374 · Question #112
An IBM WebSphere MQ client application puts messages onto remote queue RQ on queue manager QM1, which resolves to the local queue LQ on queue manager QM2. A new version of the application has been…
The correct answer is C. of the server connection channel was not changed. See the full explanation below for the reasoning.
Question
An IBM WebSphere MQ client application puts messages onto remote queue RQ on queue manager QM1, which resolves to the local queue LQ on queue manager QM2. A new version of the application has been deployed that has the capability to put messages greater than 4MB. The administrator changed the max message length attributes for the queue managers, transmission queue, sender-receiver channels and LQ to handle the larger messages. The administrator was later notified that messages greater than 4MB are still not reaching LQ. The most likely cause of the problem is the max message length attribute:
Options
- Ain file qm.ini was not changed
- Bof RQ was not changed
- Cof the server connection channel was not changed
- Dwas not set on the environment variable MQSERVER
How the community answered
(31 responses)- A6% (2)
- B6% (2)
- C84% (26)
- D3% (1)
Community Discussion
No community discussion yet for this question.