| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| DFDL call failed. Serializer being in an invalid state |
« View previous topic :: View next topic » |
| Author |
Message
|
| ottfried11 |
 Posted: Tue Mar 25, 2014 7:16 am Post subject: DFDL call failed. Serializer being in an invalid state |
 |
|
Apprentice
Joined: 28 Jun 2013
Posts: 29
|
Hi all,
we are receiving the following DFDL error message in our test environment.
| Quote: |
getDFDLSerializer,Text=DFDL call failed, due to the serializer being in an invalid state.,ErrorMessage=BIP5801E: A unknown error occurred in the DFDL parser. The operation being attempted was: 2. *** The DFDL parser signalled that an operation had failed. An error description was not provided by the parser. *** This is an internal error. Please contact your IBM support center.
|
I've had this error in debug sometimes. When a message could not be parsed correctly by the DFDL parser, all following messages could not be processed because the serializer was in an invalid state. A restart of the message broker execution group did the trick. We've never had the error in our integration (UAT) or production environment. But I'm a bit scared, because I have no idea what the error wants to tell me.
Can anyone help me on this? |
|
| Back to top |
|
 |
| kimbert |
| Posted: Tue Mar 25, 2014 8:29 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
It's an internal error. I don't think there is any specific advice that I can give. It's possible that it crops up more often in UAT because there is a lot more (re)deployment going on.
_________________
Before you criticize someone, walk a mile in their shoes. That way you're a mile away, and you have their shoes too. |
|
| Back to top |
|
|
| JosephGramig |
| Posted: Tue Mar 25, 2014 8:46 am Post subject: |
|
|
Grand Master
Joined: 09 Feb 2006
Posts: 1244
Location: Gold Coast of Florida, USA
|
| You could try changing "Parse timing" from "On Demand" to Immediate. That should make a parse failure go out the Failure terminal. |
|
| Back to top |
|
|
| ottfried11 |
| Posted: Wed Mar 26, 2014 12:31 am Post subject: |
|
|
Apprentice
Joined: 28 Jun 2013
Posts: 29
|
| As I understand it, the DFDL parser in a "on-demand" parser. Is it at all possible to set the parse timing to immediate? If yes, could you tell me where I can change the setting? I couldn't find anything in the IBM documetation or the help pages. |
|
| Back to top |
|
|
| kimbert |
| Posted: Wed Mar 26, 2014 1:59 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
The 'Parse Timing' setting is available on all Input nodes, and can be used with any on-demand parser ( DFDL, XMLNSC, MRM, XMLNS, JSON etc ).
Changing that setting will not fix this problem though. It's an internal error.
_________________
Before you criticize someone, walk a mile in their shoes. That way you're a mile away, and you have their shoes too. |
|
| 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
|
|
|
|
