2010 MQRC_DATA_LENGTH_ERROR when sending MQ messages larger than 4MB on client connection - Middleware News
2010 MQRC_DATA_LENGTH_ERROR when sending MQ messages larger than 4MB on client connection - Middleware News
Problem(Abstract)
Your WebSphere MQ client application is trying to send messages larger than 4 MB. It receives a data length error and is unable to send the messages.
Cause
The client channel did not have large enough MAXMSGL specified.
Resolving the problem
Increase the MAXMSGL attribute for the following:
* SVRCONN channel
* CLNTCONN channel
* Queue Manager
* Queue
The MAXMSGL attribute for theses MQ objects must be large enough to handle your largest messages. However, for this value to be picked up in a client channel it must be accepted by both the client and the server.
One way to do this is to define it in both the CLNTCONN channel definition and the SVRCONN channel definition using runmqsc on the server. Then copy the amqclchl.tab file from your server to the client machine, so the client can use that CLNTCONN channel definition with the new MAXMSGL value.
It is possible to put larger messages if your client application passes a channel definition structure to MQCONNX instead of calling the regular MQCONN call. There is a sample program called amqscnxc which shows how to use the MQCONNX call for specifying client connection information on the CLNTCONN channel definition.
Problem(Abstract)
Your WebSphere MQ client application is trying to send messages larger than 4 MB. It receives a data length error and is unable to send the messages.
Cause
The client channel did not have large enough MAXMSGL specified.
Resolving the problem
Increase the MAXMSGL attribute for the following:
* SVRCONN channel
* CLNTCONN channel
* Queue Manager
* Queue
The MAXMSGL attribute for theses MQ objects must be large enough to handle your largest messages. However, for this value to be picked up in a client channel it must be accepted by both the client and the server.
One way to do this is to define it in both the CLNTCONN channel definition and the SVRCONN channel definition using runmqsc on the server. Then copy the amqclchl.tab file from your server to the client machine, so the client can use that CLNTCONN channel definition with the new MAXMSGL value.
It is possible to put larger messages if your client application passes a channel definition structure to MQCONNX instead of calling the regular MQCONN call. There is a sample program called amqscnxc which shows how to use the MQCONNX call for specifying client connection information on the CLNTCONN channel definition.
Comments
Post a Comment