Author |
Message
|
gechu |
Posted: Wed Jul 07, 2010 2:12 am Post subject: Message format 'XML1' is not defined for message set |
|
|
Apprentice
Joined: 27 Feb 2008 Posts: 48
|
Hi,
Messages sometimes get backed out. After a couple of re-sends they usually get through.
I get these errors:
Error detected whilst executing the SQL statement 'InsertIntoDB();'.
Error detected whilst executing the function or procedure 'InsertIntoDB'.
Error detected whilst executing the SQL statement 'DECLARE in_ref REFERENCE TO InputRoot.MRM.myXML[1];'.
An error occurred when navigating to path element '3' of the field reference at the given location. :
Message format 'XML1' is not defined for message set 'myMessageSet (EQHDKL4002001)'.
The message set EQHDKL4002001 certainly exists and contains a definition for XML1.
How come message don´t get through all the time?
Using broker 6.x in AIX.
Regards,
Erik |
|
Back to top |
|
 |
kimbert |
Posted: Wed Jul 07, 2010 4:16 am Post subject: |
|
|
 Jedi Council
Joined: 29 Jul 2003 Posts: 5542 Location: Southampton
|
Have you redeployed this message set while the message flow was running? If so, you may find that APAR IC60120 helps. Don't be misled by the title of the APAR - it does address some timing issues with redeployed message sets. |
|
Back to top |
|
 |
gechu |
Posted: Mon Jul 12, 2010 12:34 am Post subject: |
|
|
Apprentice
Joined: 27 Feb 2008 Posts: 48
|
Thanks for your reply kimbert, but we´ve tried to deploy msg-flows and msg-sets to a new EG - still the same outcome.
Tried to find the function InsertIntoDB (which was mentioned in the debug message) in both the source code and in the files located in the broker archive file. I could not find it. Is this strange? |
|
Back to top |
|
 |
kimbert |
Posted: Mon Jul 12, 2010 4:05 am Post subject: |
|
|
 Jedi Council
Joined: 29 Jul 2003 Posts: 5542 Location: Southampton
|
Please do the following:
- Check that 'MRM' listed as the 'Primary Domain', or as one of the 'Other supported domains' in the message set?
If you are 100% sure that
a) the message is being successfully parsed by the MRM parser at least once,
and
b) a later message being processed by the same message flow in the same execution group emits the error "message format 'XML1' is not defined"
...then you should raise a PMR.
You can check a) by putting in a Trace node and checking that the tree has been built correctly by the MRM parser.
Before you raise a PMR, I strongly recommend that you get to the bottom of this error
'Error detected whilst executing the SQL statement 'InsertIntoDB();'. '
If you cannot find any such ESQL procedure in the BAR file, then it's possible that you have not deployed things fully/correctly. And that would explain the MRM error message as well. |
|
Back to top |
|
 |
gechu |
Posted: Mon Jul 12, 2010 11:34 pm Post subject: |
|
|
Apprentice
Joined: 27 Feb 2008 Posts: 48
|
I feel kind of embarrassed for involving you Kimbert now that I found out that the reason why messages "only sometimes got through" was that an instance of the msg-flow in question was deployed in a neighboring EG as well. Sorry for taking your time and thanks for trying to help me out.
/Erik |
|
Back to top |
|
 |
kimbert |
Posted: Tue Jul 13, 2010 12:34 am Post subject: |
|
|
 Jedi Council
Joined: 29 Jul 2003 Posts: 5542 Location: Southampton
|
np - thanks for the update. Next time something like this crops up I'll ask whether another copy of the flow is deployed in another EG  |
|
Back to top |
|
 |
smdavies99 |
Posted: Tue Jul 13, 2010 1:55 am Post subject: |
|
|
 Jedi Council
Joined: 10 Feb 2003 Posts: 6076 Location: Somewhere over the Rainbow this side of Never-never land.
|
kimbert wrote: |
np - thanks for the update. Next time something like this crops up I'll ask whether another copy of the flow is deployed in another EG  |
Thus expanding the list of standard questions asked by kimbert.
a.k.a. "Kimbert's Mantra"  _________________ WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
Back to top |
|
 |
kimbert |
Posted: Tue Jul 13, 2010 2:17 am Post subject: |
|
|
 Jedi Council
Joined: 29 Jul 2003 Posts: 5542 Location: Southampton
|
There was a young chap on this forum
Who would answer most threads, if he saw 'em
His reply every day
"User trace is the way"
Would more often than not simply bore 'em |
|
Back to top |
|
 |
Vitor |
Posted: Tue Jul 13, 2010 2:48 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
kimbert wrote: |
There was a young chap on this forum
Who would answer most threads, if he saw 'em
His reply every day
"User trace is the way"
Would more often than not simply bore 'em |
Yet it's the best advice  _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
|