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 HTTPInputHeader parsing in TimeoutNotificationNode

Post new topic  Reply to topic
 Strange HTTPInputHeader parsing in TimeoutNotificationNode « View previous topic :: View next topic » 
Author Message
gs
PostPosted: Thu Feb 19, 2009 1:39 am    Post subject: Strange HTTPInputHeader parsing in TimeoutNotificationNode Reply with quote

Master

Joined: 31 May 2007
Posts: 254
Location: Sweden
Hi,
I've got problems with a flow that looks like this:

MQInput -> Mapping -> JCN (create timeout request) -> TimeoutControl
TimeoutNotification -> Validate -> JCN (logging) -> MQOutput

An error is issued when the message reaches the TimeoutNotification node and the message is not backed out.

Feb 19 10:24:03 WMBTEST WebSphere Broker v6103[2650]: (BRK1T.default)[64]BIP5902W: An error occurred in parser 'Root' whilst parsing the field named 'HTTPInputHeader' on behalf of node 'MessageFlow.Timer'. The data being parsed was 'Null Buffer'. : BRK1T.9cdb0723-1f01-0000-0080-deebd0a96561: /build/S610_P/src/DataFlowEngine/ImbRootParser.cpp: 600: ImbRootParser::parseNextItem: ComIbmTimeoutNotificationNode: MessageFlow#FCMComposite_1_5
Feb 19 10:24:03 WMBTEST WebSphere Broker v6103[2650]: (BRK1T.default)[64]BIP6105E: The remaining bitstream is too small to contain an 'HTTPInputHeader' structure. : BRK1T.9cdb0723-1f01-0000-0080-deebd0a96561: /build/S610_P/src/WebServices/WSLibrary/ImbWSHeaderParsers.cpp: 236: ImbWSInputHeaderParser::refreshElementsFromBitStream: ComIbmTimeoutNotificationNode: MessageFlow#FCMComposite_1_5


Why does it even try to parse a HTTPInputHeader? I've checked the message while it resides on SYSTEM.BROKER.TIMEOUT.QUEUE and no traces of such a field. And why isn't the message backed out to a queue?

This has worked flawlessly and still works on my local WMB installation. However, it does not work on the SuSE server which has the same WMB version. Funny thing is I haven't changed anything since it was working.

WMB version 6.1.0.3
Toolkit version 6.1.0.3

I've got an PMR open for IBM...but maybe some of you guys & gals have some ideas?
Back to top
View user's profile Send private message
gs
PostPosted: Wed Mar 11, 2009 1:19 am    Post subject: Reply with quote

Master

Joined: 31 May 2007
Posts: 254
Location: Sweden
The mapping node changes the Properties header type from a MQPROPERTIESHEADER to a WSPROPERTIESHEADER.
This causes the broker to write a WSINPHDR in the message written to SYSTEM.BROKER.TIMEOUT.QUEUE.
Then of course, when the message is re-parsed, the problem with the missing HTTP input header occurs.

This was confirmed by IBM and a suggested workaround is to copy the headers and message in a compute node causing the properties header to be created with the correct parser.
The problem only affect WMB on Linux systems.
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 HTTPInputHeader parsing in TimeoutNotificationNode
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.