| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Trigger message with warning 2079 |
« View previous topic :: View next topic » |
| Author |
Message
|
| heliosfallas |
 Posted: Thu Jun 19, 2008 1:53 pm Post subject: Trigger message with warning 2079 |
 |
|
Newbie
Joined: 19 Jun 2008
Posts: 4
|
Hi guys,
I'm new to this forum and relative new to MQ Series, I've tried to get some information regarding this error, however got no results.
Here is my current scenario.
I have a WMQ 5.3 running on Win 2K3.
It has a QM and a queue with a trigger. Every time a msg arrives, it executes a vb script that uses MQAX200 object model to extract the message and upload it to a MSSQL 2K db.
I installed WMQ6 on a Win2K3, I've configured it the same way that I have it on my other server, however every time a msg arrives when the trigger is fired it returns an warning message and the data is not uploaded.
Trigger message with warning 2079
I've found this:
MQRC_TRUNCATED_MSG_ACCEPTED
Explanation:
On an MQGET call, the message length was too large to fit into the supplied buffer. The MQGMO_ACCEPT_TRUNCATED_MSG option was specified, so the call completes. The message is removed from the queue (subject to unit-of-work considerations), or, if this was a browse operation, the browse cursor is advanced to this message.
The DataLength parameter is set to the length of the message before truncation, the Buffer parameter contains as much of the message as fits, and the MQMD structure is filled in.
I thought it may be related to my GET call, however if I run the vb script manually it works fine.
It seems to be something related to the MQ trigger...
I'll appreciate your help,
Thx |
|
| Back to top |
|
 |
| Mr Butcher |
| Posted: Thu Jun 19, 2008 9:28 pm Post subject: |
|
|
Padawan
Joined: 23 May 2005
Posts: 1716
|
| Quote: |
| however every time a msg arrives when the trigger is fired it returns an warning message |
who exactly is "it" ?
_________________
Regards, Butcher |
|
| Back to top |
|
|
| heliosfallas |
| Posted: Mon Jun 23, 2008 7:17 am Post subject: |
|
|
Newbie
Joined: 19 Jun 2008
Posts: 4
|
| Mr Butcher wrote: |
| Quote: |
| however every time a msg arrives when the trigger is fired it returns an warning message |
who exactly is "it" ? |
I'm refering to the Trigger Monitor, it returns that error message.
I have started the Trigger Monitor using "runmqtrm".
The trigger is fired properly but returns that Warning Message and the data is not loaded to the SQL db.
I'll appreciate your help.
Thx |
|
| Back to top |
|
|
| heliosfallas |
| Posted: Thu Jun 26, 2008 12:00 pm Post subject: Any ideas? |
|
|
Newbie
Joined: 19 Jun 2008
Posts: 4
|
Any ideas?
I'll appreciate your help.
Thx, |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Thu Jun 26, 2008 1:08 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Take a look at the attributes of the initiation queue runmqtrm is pointing to. What is the max message length?
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| bob_buxton |
| Posted: Fri Jun 27, 2008 12:39 am Post subject: |
|
|
Master
Joined: 23 Aug 2001
Posts: 266
Location: England
|
It sounds as if the trigger monitor is getting a message that is not a trigger message.
Either the trigger monitor is pointing to the application data queue or an application is putting messages on the initiation queue
_________________
Bob Buxton
Ex-Websphere MQ Development |
|
| Back to top |
|
|
| heliosfallas |
| Posted: Mon Jun 30, 2008 9:49 am Post subject: |
|
|
Newbie
Joined: 19 Jun 2008
Posts: 4
|
| bruce2359 wrote: |
| Take a look at the attributes of the initiation queue runmqtrm is pointing to. What is the max message length? |
Max msg len is 104857600, I've verified both environments and it is even higher that what it was on my old environment. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Sat Jul 05, 2008 12:50 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| but returns that Warning Message and the data is not loaded to the SQL db. |
Sorry for the delay....
Please paste in this post the exact runmqtrm command you use to start the trigger monitor.
Please post the application queue definition, the initiation queue definition, the process definition.
Then, post all the messages from the trigger monitor - from when it starts through the 2079.
Did you look in the error logs for your qmgr? Post any related error messages here, too.
Have you googled MQAX200? I have not researched this, but did you update MQAX200 for v6?
You did not state that this application has run successfully before you installed v6. Has this application run successfully in the past?
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
