| Author |
Message
|
| Bni |
 Posted: Wed Oct 25, 2006 12:27 pm Post subject: got TRUNCATED_MSG_ACCEPTED message |
 |
|
Apprentice
Joined: 09 Aug 2006
Posts: 29
|
Our devlopers are getting TRUNCATED_MSG_ACCEPTED message when processing a message from MQ in our test server. They successfully used the same queue as late as September for testing without any problem on the server. There are no changes at all on that server. Actually there are another MQ manager running on the same MQ server and it has the same problem. The file is only 12 kilobyte, so this should not be a paramter issue on Mq side since it is maximum length the queue can handle is much much big. Our MQ version in testing is:
MQSeries Version: 520
CMVC level: p520-08-031028
The log file says:
In function ReadRequest:
START: Reading A Message
---------------------------------
In function ReadRequest:
MQGET: CC = 'WARNING', RC = 'TRUNCATED_MSG_ACCEPTED'.
THIS IS FIRST GET.
---------------------------------
In function ReadRequest:
Length of the message received = 35
---------------------------------
In function ReadRequest:
MQGET: CC = 'OK', RC = 'NONE'.
THIS IS SECOND GET.
---------------------------------
In function ReadRequest:
END: Reading A Message
---------------------------------
In function ProcessRequest:
MESSAGE: PURGE LIST OF REQUEST
---------------------------------
What could be the issue?
Any suggestions are appreciated. |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Wed Oct 25, 2006 12:46 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
It's a problem with your code.
The buffer you are supplying to the GET is smaller than the actual size of the message. Or the length of the buffer you are supplying is smaller than the actual size of the message.
Or you're using a client channel.
Also.
MQV520 is out of service. You're running a risk by using it.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Bni |
| Posted: Wed Oct 25, 2006 12:53 pm Post subject: I tend to agree with you, |
|
|
Apprentice
Joined: 09 Aug 2006
Posts: 29
|
| But the question is that they are successfully using the queue just very lately, I believe the code they are using are the same from testing and production. They don't have a problem doing the same test in another test server with the same code, the same message length( very small), and they are fine. But still I will suggest to them that they need to take a look at their code how they handle the buffer size. Thank you very much |
|
| Back to top |
|
|
| kevinf2349 |
| Posted: Wed Oct 25, 2006 1:15 pm Post subject: |
|
|
Grand Master
Joined: 28 Feb 2003
Posts: 1311
Location: USA
|
| You may also want to check the queue for a rogue (unexpected) message.....but you should really to code around this situation for the future too. |
|
| Back to top |
|
|
| Bni |
| Posted: Wed Nov 01, 2006 8:30 am Post subject: Developers are saying that only mutiples of 8 k file |
|
|
Apprentice
Joined: 09 Aug 2006
Posts: 29
|
| is written to a file. For example, of 8k size file is sent, it can get it, but if the size is 12 k, 3 k will be lost. I tend to think it is a code issue, the only problem that I cannot figure out is that according to developers, the code base is the same across broad from several productions servers and to several test servers. They only recently found this issue on this test server. By the way we applied the patch to 5.2 version on April, but they did sucessful test as late as September, so I don't believe it is a patch issue. I am asking them to code more specific with linked JMS exceptions to see if we can see some specific error code. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Nov 01, 2006 8:34 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
If you're getting TRUNCATED_MESSAGE_ACCEPTED, especially where the max mesage size on the queue is more than sufficient to handle the message, then this is a coding issue.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mvic |
| Posted: Thu Nov 02, 2006 1:42 am Post subject: Re: got TRUNCATED_MSG_ACCEPTED message |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
| Bni wrote: |
In function ReadRequest:
MQGET: CC = 'WARNING', RC = 'TRUNCATED_MSG_ACCEPTED'. |
Since this is output from your code using (I assume) a mapping function to turn a reason code into some text, there is potentially a doubt over whether the mapping has been done right. However... supposing the developers have done the right mapping... MQRC_TRUNCATED_MSG_ACCEPTED is given when, for example,
* MQGET is called, with a buffer of 1000 bytes in length and MQGMO_ACCEPT_TRUNCATED_MSG in the MQGMO.Options.
* The queue manager then identifies a suitable message which is more than 1000 bytes in length. Only the first 1000 bytes are copied to the buffer, and the call returns with MQRC_TRUNCATED_MSG_ACCEPTED.
The above can happen with no change to app code, it just takes a larger-than-normal message to cause this sort of thing.
If the developers do not want to receive a partial message, they should omit MQGMO_ACCEPT_TRUNCATED_MSG from the MQGMO.Options on the MQGET call. They should then be prepared to accept MQRC_TRUNCATED_MSG_FAILED on return from MQGET. |
|
| Back to top |
|
|
|
|
