ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Strange behaviour of MB

Post new topic  Reply to topic
 Strange behaviour of MB « View previous topic :: View next topic » 
Author Message
Gemz
PostPosted: Tue Jul 08, 2008 1:44 am    Post subject: Strange behaviour of MB Reply with quote

Centurion

Joined: 14 Jan 2008
Posts: 124

Hi,

We are using MB v6.1 in AIX.

We are using message sets for validating the input message in File Input node and using JCN to insert the data into DB.

When the files to process are very huge in number, few files are failed to parse and getting the below Exception.

Quote:
Inner Exception: PARSEREXCEPTION
FILE: /build/S000_P/src/DataFlowEngine/ImbRootParser.cpp
LINE: 586
FUNCTION: ImbRootParser::parseNextItem
TYPE: ComIbmFileInputNode
NAME: OMS_IAR_01_ITEM#FCMComposite_1_1
LABEL: OMS_IAR_01_ITEM.OMSFileInput
CATALOG: BIPv610
SEVERITY: 2
NUMBER: 5902
TEXT: Exception whilst parsing
TEXT: Root
TEXT: MRM
TEXT: Stream Based Buffer - no stream data read in yet.
Inner Exception: PARSEREXCEPTION
FILE: /build/S000_P/src/MTI/MTIforBroker/MtiImbParser2/MtiImbParser.cpp
LINE: 508
FUNCTION: MtiImbParser::parseFirstChild
TYPE: ComIbmFileInputNode
NAME: OMS_IAR_01_ITEM#FCMComposite_1_1
LABEL: OMS_IAR_01_ITEM.OMSFileInput
CATALOG: BIPv610
SEVERITY: 3
NUMBER: 5285
TEXT: ImbRecoverableException caught from worker->parseNext.
TEXT: OMS_ITEM_INS
TEXT: 1
TEXT: CSV
TEXT: /omsItemMessage/omsItem/omsItemName
Inner Exception: PARSEREXCEPTION
FILE: /build/S000_P/src/cpi/pwf/nxd/nxdworker.cpp
LINE: 462
FUNCTION: NXDWorker::parseNext
CATALOG: BIPv610
SEVERITY: 1
NUMBER: 5421
TEXT: TDS General Error
TEXT: omsItemMessage
TEXT: /omsItemMessage/omsItem(746 of unbounded)
TEXT: 69632
Inner Exception: PARSEREXCEPTION
FILE: /build/S000_P/src/MTI/MTIforBroker/MtiImbParser2/MtiImbFIHandler.cpp
LINE: 3931
FUNCTION: MtiImbFIHandler::attachDefaultElement
CATALOG: BIPv610
SEVERITY: 3
NUMBER: 5374
TEXT: An element has been deemed complete occurring less than specified minOccurs
TEXT: 61^measurementseriesNo
TEXT: 0
TEXT: 1
TEXT: omsItem
TEXT: 746


If we put the same file again in the file input path, those files(previously failed to parse) are parsed successfully.
In the Exception lise i could see like 'Stream Based Buffer - no stream data read in yet.'
Is this the know behaviour or any body else faced these issues.

Thanks
Back to top
View user's profile Send private message
kimbert
PostPosted: Tue Jul 08, 2008 3:47 am    Post subject: Reply with quote

Jedi Council

Joined: 29 Jul 2003
Posts: 5542
Location: Southampton

This entry:
Quote:
Stream Based Buffer - no stream data read in yet.

can be safely ignored whenever it occurs. It is not the problem.

The real problem is that the 'same' message is sometimes failing validation, and sometimes passing validation. That sounds like a defect in the product, but before you raise a PMR, you could find out whether it is the File node that is causing the problem. If possible ( i.e. if these huge files can be handled by MQ ), can you retry using an MQInput node instead of FileInput. Inhibit gets on the input queue, put as many as possible of your messages on it, then let them all flow through.
Back to top
View user's profile Send private message
Gemz
PostPosted: Tue Jul 08, 2008 5:15 am    Post subject: Reply with quote

Centurion

Joined: 14 Jan 2008
Posts: 124

When using MQ, messages are processed and I did not get such parser exception.

When using file input node this happens rarely.
Back to top
View user's profile Send private message
sridhsri
PostPosted: Tue Jul 08, 2008 6:48 pm    Post subject: Reply with quote

Master

Joined: 19 Jun 2008
Posts: 297

I was talking to a colleague of mine and he said there was a timing issue between the FileInput node's parser and the TDS parser. Now, I am not sure if this is what you are facing. One solution that we used was if you could parse it from the file input as a blob and put it on queue. then use the mqinput node to read (esp. since you are not getting the same error from mqinput).
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Tue Jul 08, 2008 7:15 pm    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY

Gemz wrote:
NUMBER: 5374
TEXT: An element has been deemed complete occurring less than specified minOccurs
TEXT: 61^measurementseriesNo

TEXT: 0


Don't know if it is due to speed differential but it looks like your message does not conform to your model.
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
kimbert
PostPosted: Wed Jul 09, 2008 1:22 am    Post subject: Reply with quote

Jedi Council

Joined: 29 Jul 2003
Posts: 5542
Location: Southampton

Gemz,

Please raise a PMR for this. You might want to make absolutely sure that MQ does not exhibit the same problem, because IBM's service dept are sure to ask that question.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Strange behaviour of MB
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.