|  | 
 
  
    | RSS Feed - WebSphere MQ Support | RSS Feed - Message Broker Support |  
 
  
	|    |  |  
  
	| Removing temporary queue... | « View previous topic :: View next topic » |  
  	| 
		
		
		  | Author | Message |  
		  | sonalzade | 
			  
				|  Posted: Mon Nov 26, 2012 6:38 am    Post subject: Removing temporary queue... |   |  |  
		  | Newbie
 
 
 Joined: 16 Oct 2012Posts: 5
 
 
 | 
			  
				| Hi, 
 I am seeking for your help to resolve one requirement.
 
 In the system, there are different subflows which communicates to different systems. We get input message from queue in the Main Flow and the same is passed to a Routing Sub Flow. Here we can not replace the Routing Sub Flow with the Route node as to determine routing we need to call few services etc. The Routing Sub Flow based on processing output determines to which subflow to route the incoming message. The processing message is not required once Routing destination is determined.
 
 Currently it implemented as follow: message enters Routing Sub Flow which first stores the incoming message to one temp queue. It then processes transaction, determines the Routing destination and then picks up the incoming message from the temp queue and forwards to the appropriate destination sub flow.
 
 Now the defect is raised mentioning that the temp queue is redundant and we should store the incoming message in env variable and look it up later and forward to destination sub flow.
 
 We tried the solution by storing incoming message in env variable and later forwarding to sub flow. It is successful for one sub flow but in the other where a collector node is used, it's failing. The collector node in the destination sub flow is throwing below exception: BIPmsgs: 6105, Invalid buffer parameters and also mentioning about HTTPInputHeader and WSINPHDR. Pls find the exception text below. The flow then stucks going in an infinite loop, getting stucked in Collector node.
 
 
 ExceptionList
 RecoverableException
 File:CHARACTER:/build/S700_P/src/DataFlowEngine/ImbDataFlowNode.cpp
 Line:INTEGER:1083
 Function:CHARACTER:ImbDataFlowNode::createExceptionList
 Type:CHARACTER:ComIbmCollectorNode
 Name:CHARACTER:EB_270_ROUTE_MAIN_FLOW#FCMComposite_1_20.EB_270_MAPTO_271FACADEREQUEST_SUB_FLOW#FCMComposite_1_1
 Label:CHARACTER:EB_270_ROUTE_MAIN_FLOW.EB_270_MAPTO_271FACADEREQUEST_SUB_FLOW.Collector
 Catalog:CHARACTER:BIPmsgs
 Severity:INTEGER:3
 Number:INTEGER:2230
 Text:CHARACTER:Node throwing exception
 ParserException
 File:CHARACTER:/build/S700_P/src/DataFlowEngine/ImbRootParser.cpp
 Line:INTEGER:816
 Function:CHARACTER:ImbRootParser::parseNextItem
 Type:CHARACTER:ComIbmCollectorNode
 Name:CHARACTER:EB_270_ROUTE_MAIN_FLOW#FCMComposite_1_20.EB_270_MAPTO_271FACADEREQUEST_SUB_FLOW#FCMComposite_1_1
 Label:CHARACTER:EB_270_ROUTE_MAIN_FLOW.EB_270_MAPTO_271FACADEREQUEST_SUB_FLOW.Collector
 Catalog:CHARACTER:BIPmsgs
 Severity:INTEGER:2
 Number:INTEGER:5902
 Text:CHARACTER:Exception whilst parsing
 Insert
 Type:INTEGER:5
 Text:CHARACTER:Root
 Insert
 Type:INTEGER:5
 Text:CHARACTER:HTTPInputHeader
 Insert
 Type:INTEGER:5
 Text:CHARACTER:Null Buffer
 ParserException
 File:CHARACTER:/build/S700_P/src/WebServices/WSLibrary/ImbWSHeaderParsers.cpp
 Line:INTEGER:249
 Function:CHARACTER:ImbWSInputHeaderParser::refreshElementsFromBitStream
 Type:CHARACTER:ComIbmCollectorNode
 Name:CHARACTER:EB_270_ROUTE_MAIN_FLOW#FCMComposite_1_20.EB_270_MAPTO_271FACADEREQUEST_SUB_FLOW#FCMComposite_1_1
 Label:CHARACTER:EB_270_ROUTE_MAIN_FLOW.EB_270_MAPTO_271FACADEREQUEST_SUB_FLOW.Collector
 Catalog:CHARACTER:BIPmsgs
 Severity:INTEGER:3
 Number:INTEGER:6105
 Text:CHARACTER:Invalid buffer parameters
 Insert
 Type:INTEGER:5
 Text:CHARACTER:HTTPInputHeader
 Insert
 Type:INTEGER:5
 Text:CHARACTER:WSINPHDR
 
 
 
 We googled for the exception and found only one relevant post:
 http://www.mqseries.net/phpBB/viewtopic.php?p=241606&sid=2d90d4da8ea58db1f219eafca844d53e
 
 The exception in the above post is Null Buffer but we are getting Invalid Buffer parameters but initially we got this exception as well). The reply mentions that this problem occurs in Linux system, the system which we are using. We are already using the java compute node to copy the message headers and the incoming message to BLOB/BLOB. But we are still getting above mentioned exception.
 
 We even tried to propagate the exact same incoming message. We stored incoming message in map against correlationId and then upon determining Routing destination, look up the same incoming MbMessage from the map against correlationId and forward to sub flow. But the issue persists.
 
 Here are the Broker details:
 OS Name: Linux
 OS Version: #1 SMP 2010-05-20 11:14:20 +0200
 OS Architechture: s390x
 WMB Version: 7.0.0.5
 Build Level: S700-FP05
 
 Pl advise. Looking forward to getting your reply.
 
 Thanks n regards,
 
 Sonal Zade
 |  |  
		  | Back to top |  |  
		  |  |  
		  | lancelotlinc | 
			  
				|  Posted: Mon Nov 26, 2012 6:41 am    Post subject: |   |  |  
		  |  Jedi Knight
 
 
 Joined: 22 Mar 2010Posts: 4941
 Location: Bloomington, IL USA
 
 | 
			  
				| You have to associate a parser with the data and reset the data to OutputRoot once in the subflow but before the collector node. _________________
 http://leanpub.com/IIB_Tips_and_Tricks
 Save $20: Coupon Code: MQSERIES_READER
 |  |  
		  | Back to top |  |  
		  |  |  
		  | smdavies99 | 
			  
				|  Posted: Mon Nov 26, 2012 7:00 am    Post subject: |   |  |  
		  |  Jedi Council
 
 
 Joined: 10 Feb 2003Posts: 6076
 Location: Somewhere over the Rainbow this side of Never-never land.
 
 | 
			  
				| 
   
	| Quote: |  
	| It is successful for one sub flow but in the other where a collector node is used, it's failing. The collector node in the destination sub flow is throwing below exception |  
 It is essential to understand that the output of a message from a collector is just that, a collection.
 It can have everything that was sent to it inside. This includes
 Properties Folders
 Message Headers (be it MQ, HTTP etc)
 Multiple sets of data.
 
 Add a Trace node and set it tp output ${Root} on the output from the Collector node.
 Then you will see the structure you will have to sort out before you can output it somewhere.
 
 Enjoy!
 _________________
 WMQ User since 1999
 MQSI/WBI/WMB/'Thingy' User since 2002
 Linux user since 1995
 
 Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions.
 |  |  
		  | Back to top |  |  
		  |  |  
		  | sonalzade | 
			  
				|  Posted: Tue Nov 27, 2012 3:26 am    Post subject: |   |  |  
		  | Newbie
 
 
 Joined: 16 Oct 2012Posts: 5
 
 
 | 
			  
				| Hi everybody ! 
 Thanks a lot for your help and suggestions. Appreciate it
   
 
 Thanks !
 
 Sonal Zade
 |  |  
		  | 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
 
 |  |  |  |