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:

Queue managers QMGR1 and QMGR2 are members of cluster QMCLUS.
An application connected to QMGR1 needs to send messages to a local queue APP.LOCAL of QMGR2.
The administrator creates the following definitions:
On QMGR1: DEFINE QALIAS(APP.ALIAS) + TARGET(APP.LOCAL) + CLUSTER(QMCLUS) On QMGR2: DEFINE QLOCAL(APP.LOCAL) + MAXDEPTH(50000)
The administrator is notified that the application is unable to send messages to APP.LOCAL.

What is the most likely cause?

An administrator created a queue manager for an application using the command: crtmqm TESTQMGR The application is started by triggering, and puts forty 3.5MB persistent messages onto a remote queue. The administrator is notified that the IBM WebSphere MQ error logs are getting populated with errors whenever the application is started.
What could be the likely cause?