|  | 
 
  
    | RSS Feed - WebSphere MQ Support | RSS Feed - Message Broker Support |  
 
  
	|    |  |  
  
	| Wrong type in both mapped and source token on MQOutput? | « View previous topic :: View next topic » |  
  	| 
		
		
		  | Author | Message |  
		  | junaid | 
			  
				|  Posted: Thu Dec 26, 2019 7:34 am    Post subject: Wrong type in both mapped and source token on MQOutput? |   |  |  
		  | Acolyte
 
 
 Joined: 29 Nov 2018Posts: 58
 
 
 | 
			  
				| Hi, 
 I am using mq queue for initiating logging flow . WS-Security with X.509 is applied on both consumer and provider soap nodes
 
 My Flows are like
 
 SOAP Consumer >    SOAPInput >  SOAPRequest > SOAPReply
 SOAP Provider >    SOAPInput > mapping> flow order 1 > esql >  mqout > log4J   >   Flow order 2 >  soaprequest > esql > soap reply (to consumer)
 
 when writing message  in mqout following exception is coming .
 
 
 
 
   
	| Quote: |  
	| <exceptionList> <RecoverableException>
 <File>/build/slot3/S1000_P/src/DataFlowEngine/MessageServices/ImbDataFlowNode.cpp</File>
 <Line>1251</Line>
 <Function>ImbDataFlowNode::createExceptionList</Function>
 <Type>ComIbmMQOutputNode</Type>
 <Name>BrokerSchema/Main#FCMComposite_1_23</Name>
 <Label>BrokerSchema.Main.MQ Output1</Label>
 <Catalog>BIPmsgs</Catalog>
 <Severity>3</Severity>
 <Number>2230</Number>
 <Text>Node throwing exception</Text>
 <Insert>
 <Type>14</Type>
 <Text>BrokerSchema.FTMain.MQ Output1</Text>
 </Insert>
 <RecoverableException>
 <File>/build/slot3/S1000_P/src/DataFlowEngine/MessageServices/ImbSecurityManager.cpp</File>
 <Line>1363</Line>
 <Function>ImbSecurityManager::retrieveIdentityToPropagate</Function>
 <Type/>
 <Name/>
 <Label/>
 <Catalog>BIPmsgs</Catalog>
 <Severity>3</Severity>
 <Number>2720</Number>
 <Text>Wrong type in both mapped and source token</Text>
 <Insert>
 <Type>5</Type>
 <Text>username, usernameAndPassword</Text>
 </Insert>
 <Insert>
 <Type>5</Type>
 <Text/>
 </Insert>
 </RecoverableException>
 </RecoverableException>
 </exceptionList>
 
 |  |  |  
		  | Back to top |  |  
		  |  |  
		  | Vitor | 
			  
				|  Posted: Fri Dec 27, 2019 6:41 am    Post subject: Re: Wrong type in both mapped and source token on MQOutput? |   |  |  
		  |  Grand High Poobah
 
 
 Joined: 11 Nov 2005Posts: 26093
 Location: Texas, USA
 
 | 
			  
				| 
   
	| junaid wrote: |  
	| <Text>Wrong type in both mapped and source token</Text>
 
 |  
 Seems clear enough; you think you're correctly using X.509, the software disagrees with you.
 
 What version of broker? How have you configured X.509? Does this work in other parts of your installation?
 _________________
 Honesty is the best policy.
 Insanity is the best defence.
 |  |  
		  | Back to top |  |  
		  |  |  
		  | fjb_saper | 
			  
				|  Posted: Fri Dec 27, 2019 7:08 am    Post subject: Re: Wrong type in both mapped and source token on MQOutput? |   |  |  
		  |  Grand High Poobah
 
 
 Joined: 18 Nov 2003Posts: 20767
 Location: LI,NY
 
 | 
			  
				| 
   
	| Vitor wrote: |  
	| 
   
	| junaid wrote: |  
	| <Text>Wrong type in both mapped and source token</Text>
 
 |  
 Seems clear enough; you think you're correctly using X.509, the software disagrees with you.
 
 What version of broker? How have you configured X.509? Does this work in other parts of your installation?
 |  
 I'm thinking this is specific to the MQ node. The identity is propagated from the Soap Input node and of course doesn't match what is needed for MQ. Hence the MQ node fails... probably with a reason code of 2035?
  _________________
 MQ & Broker admin
 |  |  
		  | Back to top |  |  
		  |  |  
		  | Vitor | 
			  
				|  Posted: Thu Jan 02, 2020 5:30 am    Post subject: Re: Wrong type in both mapped and source token on MQOutput? |   |  |  
		  |  Grand High Poobah
 
 
 Joined: 11 Nov 2005Posts: 26093
 Location: Texas, USA
 
 | 
			  
				| 
   
	| fjb_saper wrote: |  
	| 
   
	| Vitor wrote: |  
	| 
   
	| junaid wrote: |  
	| <Text>Wrong type in both mapped and source token</Text>
 
 |  
 Seems clear enough; you think you're correctly using X.509, the software disagrees with you.
 
 What version of broker? How have you configured X.509? Does this work in other parts of your installation?
 |  
 I'm thinking this is specific to the MQ node. The identity is propagated from the Soap Input node and of course doesn't match what is needed for MQ. Hence the MQ node fails... probably with a reason code of 2035?
  |  
 
 Oooo.... nice catch....I missed that MQOut in the process flow!
 _________________
 Honesty is the best policy.
 Insanity is the best defence.
 |  |  
		  | 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
 
 |  |  |  |