| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Parser Exception with debugger |
« View previous topic :: View next topic » |
| Author |
Message
|
| deepak_paul |
 Posted: Sun Oct 23, 2011 9:47 am Post subject: Parser Exception with debugger |
 |
|
Centurion
Joined: 04 Oct 2008
Posts: 147
Location: US
|
All,
I am getting below ParserException("Validation is enabled but no message set has been specified") when i enabled the debugger on the message flow.
| Code: |
ExceptionList
RecoverableException
File:CHARACTER:/build/S700_P/src/DataFlowEngine/ImbDataFlowNode.cpp
Line:INTEGER:1073
Function:CHARACTER:ImbDataFlowNode::createExceptionList
Type:CHARACTER:ComIbmTryCatchNode
Name:CHARACTER:com/premierinc/dacq/clinical/MFRealTimeClinicalpXSDFormat#FCMComposite_1_9
Label:CHARACTER:com.premierinc.dacq.clinical.MFRealTimeClinicalpXSDFormat.Try Catch
Catalog:CHARACTER:BIPmsgs
Severity:INTEGER:3
Number:INTEGER:2230
Text:CHARACTER:Node throwing exception
RecoverableException
File:CHARACTER:/build/S700_P/src/DataFlowEngine/ImbComputeNode.cpp
Line:INTEGER:489
Function:CHARACTER:ImbComputeNode::evaluate
Type:CHARACTER:ComIbmComputeNode
Name:CHARACTER:com/premierinc/dacq/clinical/MFRealTimeClinicalpXSDFormat#FCMComposite_1_4.com/premierinc/dacq/transformation/SFpXSDtopXSDplusTransform#FCMComposite_1_1
Label:CHARACTER:com.premierinc.dacq.clinical.MFRealTimeClinicalpXSDFormat.SFpXSDtopXSDplusTransform.Transform_to_pXSDplus
Catalog:CHARACTER:BIPmsgs
Severity:INTEGER:3
Number:INTEGER:2230
Text:CHARACTER:Caught exception and rethrowing
RecoverableException
File:CHARACTER:/build/S700_P/src/DataFlowEngine/ImbRdl/ImbRdlStatementGroup.cpp
Line:INTEGER:641
Function:CHARACTER:SqlStatementGroup::execute
Type:CHARACTER:ComIbmComputeNode
Name:CHARACTER:com/premierinc/dacq/clinical/MFRealTimeClinicalpXSDFormat#FCMComposite_1_4.com/premierinc/dacq/transformation/SFpXSDtopXSDplusTransform#FCMComposite_1_1
Label:CHARACTER:com.premierinc.dacq.clinical.MFRealTimeClinicalpXSDFormat.SFpXSDtopXSDplusTransform.Transform_to_pXSDplus
Catalog:CHARACTER:BIPmsgs
Severity:INTEGER:3
Number:INTEGER:2488
Text:CHARACTER:Error detected, rethrowing
Insert
Type:INTEGER:5
Text:CHARACTER:com.premierinc.dacq.transformation.pXSDplus_Xform_Stub_Compute.Main
Insert
Type:INTEGER:5
Text:CHARACTER:20.3
Insert
Type:INTEGER:5
Text:CHARACTER:DECLARE I INTEGER 1;
ParserException
File:CHARACTER:/build/S700_P/src/MTI/MTIforBroker/GenXmlParser4/ImbXMLNSCDocHandler.cpp
Line:INTEGER:129
Function:CHARACTER:ImbXMLNSCDocHandler::setCachedIRForMessageSet
Type:CHARACTER:
Name:CHARACTER:
Label:CHARACTER:
Catalog:CHARACTER:BIPmsgs
Severity:INTEGER:3
Number:INTEGER:5027
Text:CHARACTER:Validation is enabled but no message set has been specified
|
I have set the message set as below.
| Code: |
DECLARE setName CHARACTER 'MS_DACQ_pXSDMsgDef';
DECLARE typeName CHARACTER 'Message';
DECLARE formatName CHARACTER 'XML1';
DECLARE options INTEGER BITOR(ValidateContentAndValue, ValidateException, ValidateComplete);
DECLARE bEnvVarTrmdMsg BLOB ASBITSTREAM(Environment.Variables.DatabaseSave.TrnfrmdMsg,inEncoding,inCCSID);
CREATE LASTCHILD OF OutputRoot DOMAIN('XMLNSC') PARSE(bEnvVarTrmdMsg, inEncoding, inCCSID, setName, typeName, formatName, options);
|
1. When i disconnected the debugger and ran the message flow, i did not have any exception raised from message flow and it passed all the modules and message flow completed successfully.
2. When i disconnected the debugger, I have enabled user trace and confirmed that there was no issue with the message flow and i could see the message flow completed successfully.
3. I have made sure that I have set the message set name using one of the options mentioned in the below url. http://publib.boulder.ibm.com/infocenter/wmbhelp/v7r0m0/topic/com.ibm.etools.mft.bipmsgs.doc/ay_bip5.htm?resultof=%22%42%49%50%35%30%32%37%22%20%22%62%69%70%35%30%32%37%22%20
4. After above all behavior, it now makes me suspect that debugger is causing that Parser Exception.
5. I have explored little bit on this issue and found below thread in mqseries.net,
http://www.mqseries.net/phpBB2/viewtopic.php?t=49318 where
| kimbert wrote: |
...I suspect that you are trying to debug a parser problem using the message flow debugger. If so, don't. The standard advice is
- Disconnect the debugger
- Insert Trace nodes wherever you need to inspect the contents of the message tree
- Take a user trace while the message is passing througth the flow.
The debugger is good for all kinds of purposes, but not for debugging parsing errors. And user trace is very useful for all kinds of other purposes, and well worth getting familiar with. |
Just wondering to see why debugger is causing this kind of exception.
_________________
Regards
Paul |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Sun Oct 23, 2011 10:29 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
I believe that the XMLNSC parser only supports a single message format, and so specifying anything at all, particularly specifying the name of the default xml format for MRM, is not going to provide any added value. I won't state that this causes a problem, but it could be contributing.
Take a user trace. Don't bother with Debugger. Even in modern releases, although vastly vastly vastly improved over previous versions, debugger can provide a skewed view of what's being processed.
Likely the issue is being caused in this case because the debugger is forcing a full parse of the message tree. Why that's causing an issue now when it doesn't cause the issue at other points in the code is unknown from the information you have provided... |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Sun Oct 23, 2011 10:42 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
I personally tend to rely more on Trace nodes now that they can be disabled in production. Using Trace nodes rather than the debugger gives a more accurate picture of what is being processed, especially if what you are doing relies on timing (Web Services).
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| deepak_paul |
| Posted: Sun Oct 23, 2011 11:17 am Post subject: |
|
|
Centurion
Joined: 04 Oct 2008
Posts: 147
Location: US
|
| mqjeff wrote: |
...Take a user trace. Don't bother with Debugger. Even in modern releases, although vastly vastly vastly improved over previous versions, debugger can provide a skewed view of what's being processed.
Likely the issue is being caused in this case because the debugger is forcing a full parse of the message tree. Why that's causing an issue now when it doesn't cause the issue at other points in the code is unknown from the information you have provided... |
I took the user trace and went through completely that there is no exception raised in any of the modules in the message flow. Is there a way we can get support from IBM on this or we have to take this as a known behavior.
_________________
Regards
Paul |
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Oct 24, 2011 1:46 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| deepak_paul wrote: |
| mqjeff wrote: |
...Take a user trace. Don't bother with Debugger. Even in modern releases, although vastly vastly vastly improved over previous versions, debugger can provide a skewed view of what's being processed.
Likely the issue is being caused in this case because the debugger is forcing a full parse of the message tree. Why that's causing an issue now when it doesn't cause the issue at other points in the code is unknown from the information you have provided... |
I took the user trace and went through completely that there is no exception raised in any of the modules in the message flow. Is there a way we can get support from IBM on this or we have to take this as a known behavior. |
You can certainly open PMRS against the debugger. |
|
| Back to top |
|
|
| mqxplorer |
| Posted: Tue Jan 17, 2012 2:21 pm Post subject: |
|
|
Master
Joined: 22 Jun 2009
Posts: 206
|
| mqjeff wrote: |
| deepak_paul wrote: |
| mqjeff wrote: |
...Take a user trace. Don't bother with Debugger. Even in modern releases, although vastly vastly vastly improved over previous versions, debugger can provide a skewed view of what's being processed.
Likely the issue is being caused in this case because the debugger is forcing a full parse of the message tree. Why that's causing an issue now when it doesn't cause the issue at other points in the code is unknown from the information you have provided... |
I took the user trace and went through completely that there is no exception raised in any of the modules in the message flow. Is there a way we can get support from IBM on this or we have to take this as a known behavior. |
You can certainly open PMRS against the debugger. |
I am facing the same issue... Did you open the PMR? If so, what was the response from IBM?
Thanks
mqxplorer |
|
| Back to top |
|
|
| kimbert |
| Posted: Wed Jan 18, 2012 2:31 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
Are you 100% sure that the message flow works correctly when the debugger is disconnected?
If the answers is 'yes' then please raise a PMR. But post the error that you are getting first, in case we can help you to diagnose the problem. |
|
| 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
|
|
|
|
