|   | 
	 
  
    | 
RSS Feed - WebSphere MQ Support
 | 
RSS Feed - Message Broker Support
 |   
 
  
	     | 
	 | 
   
 
  
	|  Recoverable Exception 2617 | 
	« View previous topic :: View next topic »  | 
   
  
  	
	  
		
		
		  | Author | 
		  Message
		 |  
		
		  | biswagourab | 
		  
		    
			  
				 Posted: Mon Oct 24, 2005 12:59 pm    Post subject: Recoverable Exception 2617 | 
				     | 
			   
			 
		   | 
		 
		
		    Apprentice
 
 Joined: 31 May 2005 Posts: 47 Location: London 
  | 
		  
		    
			  
				Hi 
 
   I tried to debug my flow in MQSI 2.1, the compute node is properly implemented and the XML parsed, but when it reaches the Output Node, it throws an exception, and the flow fails. 
 
It says Recoverable Exception 2617. 
 
   I am using a destination list in the output node and also using the CASE statement to select the output queues depending  on the value they get from the MQMD field in the input. 
 
 
Please tell me what should I do ?
 
 
Waiting for your replies
 
 Regards 
 
Biswa | 
			   
			 
		   | 
		 
		
		  | Back to top | 
		  
		  	
		   | 
		 
		
		    | 
		 
		
		  | JT | 
		  
		    
			  
				 Posted: Mon Oct 24, 2005 7:20 pm    Post subject:  | 
				     | 
			   
			 
		   | 
		 
		
		   Padawan
 
 Joined: 27 Mar 2003 Posts: 1564 Location: Hartford, CT. 
  | 
		  
		    
			  
				Place a Trace node, with the $Root pattern, after the Compute node and prior to the MQOutput node. Review the trace to ensure the proper format of the MQMD, and that a message payload is present.
 
 
   
	| Quote: | 
   
  
	BIP2617
 
Severity
 
20 : Error
 
 
Message
 
Output message is empty; output node '<insert_0>'.
 
 
Explanation
 
The WebSphere Business Integration Message Brokers output node '<insert_0>' has received a message to write to an WebSphere Business Integration output queue, but the message appears to be empty. This error may be generated when 1) there is no MQMD and no message content in the output bitstream (there really is no data) or 2) there is no MQMD and the size of the message content is less that the size of the MQMD (it appears there is no content). This situation can occur when a output message is built incorrectly using the Compute node.
 
 
Response
 
Check the message flow to determine whether the message is being built correctly. If not, correct the problem and redeploy the broker. | 
   
 
 
 
Since you're using a DestinationList, did you set the proper value (Destination List) for the Destination Mode on the MQOutput node ? | 
			   
			 
		   | 
		 
		
		  | 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
  | 
  		 
	   
	 | 
   
 
  	 | 
	  |