Here's the part of our code that sends the message, but I'm not sure how much it will help. The size of the string response that it fails on is 4227742 characters. It works fine for all smaller mess ...
We have a C++ application (using MQ's C API) that is trying to place a large (~6 MB) message onto a temporary dynamic queue. The put fails with RC 2010 - data length error.
I am now receiving messages but even after I parse out the MQRFH info I'm still getting messages that just say "RFH" when I print them out. I can retrieve the message from the character buffer by sea ...
Thanks for the tip - I hadn't used that tool before. From the output it looks like we just have a mismatch in subscription topics - I had "topic://topicname" and JMS interprets that for MQ as just "t ...
I am trying to use MQSeries pub/sub between JMS and non-JMS. My non-JMS user can receive non-JMS publications but doesn't receive any messages when subscribing to JMS publications.