| Author |
Message
|
| Jithesh shetty |
 Posted: Thu Nov 15, 2007 12:47 am Post subject: TDS to XMl.. |
 |
|
Acolyte
Joined: 30 Oct 2007
Posts: 51
|
hi,
i have created simple message flow..MQinput->Compute->Mqoutput..to convert tds to XMl ...
i have created message set for TDS....but when running the flow..folllowing error is showing in debugger.
ImbRecoverableException caught from worker->initializeParse/setFIHandler.
please hep me in this....... |
|
| Back to top |
|
 |
| Jithesh shetty |
| Posted: Thu Nov 15, 2007 12:48 am Post subject: Re: TDS to XMl.. |
|
|
Acolyte
Joined: 30 Oct 2007
Posts: 51
|
| Jithesh shetty wrote: |
hi,
i have created simple message flow..MQinput->Compute->Mqoutput..to convert tds to XMl ...
i have created message set for TDS....but when running the flow..folllowing error is showing in debugger.
error:
ImbRecoverableException caught from worker->initializeParse/setFIHandler.
i a sending the i/p TDS msg..
VMI;INVRPT;VMI_INVRPTD97A_1553;VMI;040611121212;062011121212;032;5038495000019;0027855;GBP;0563754455;1232-2141-5212;VMI;WOKHOhosub/4077;100
VMI;INVRPT;VMI_INVRPTD97A_1553;VMI;040611121212;062011121212;032;5038495000019;0027855;GBP;0812344365;1232-2141-6961;VMI;WOKHOhosub/4066;100
please hep me in this....... |
|
|
| Back to top |
|
|
| AkankshA |
| Posted: Thu Nov 15, 2007 1:08 am Post subject: Re: TDS to XMl.. |
|
|
Grand Master
Joined: 12 Jan 2006
Posts: 1494
Location: Singapore
|
| Jithesh shetty wrote: |
ImbRecoverableException caught from worker->initializeParse/setFIHandler.
. |
indicates parser failure.....
and since we dont know your TDS msg set definition, so we wont be able to narrow down to the exact cause...
_________________
Cheers |
|
| Back to top |
|
|
| Jithesh shetty |
| Posted: Thu Nov 15, 2007 1:45 am Post subject: TDS to XMl.. |
|
|
Acolyte
Joined: 30 Oct 2007
Posts: 51
|
| how to resolve this problem.......????? |
|
| Back to top |
|
|
| kimbert |
| Posted: Thu Nov 15, 2007 3:29 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
I've said this more times than I care to remember now, but here goes again...
- When there is a parsing error in WMB, you always get a chain of exceptions. The first one in the chain will give specific information about the parsing error. The higher-level exceptions are less useful ( as Jithesh shetty has found ).
- The debugger usually only shows the least useful exception. That's unfortunate, and will get fixed sometime.
The solution is to detach the debugger and take a user trace. That way, you will get the complete text of all the parsing exceptions. The debugger is a poor tool for diagnosing parsing problems anyway. When you upgrade to v6.1 user trace will be even more useful. The v6.1 debug-level user trace contains a trace of the TDS parser's activities. |
|
| Back to top |
|
|
|
|
