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 » Problem with JMSInput Node

Post new topic  Reply to topic
 Problem with JMSInput Node « View previous topic :: View next topic » 
Author Message
jorro004
PostPosted: Tue Sep 25, 2007 1:41 pm    Post subject: Problem with JMSInput Node Reply with quote

Acolyte

Joined: 25 Aug 2007
Posts: 50

Hi ,

I have a flow where the message comes from the JMSInput Node and then transformation happens. I configured failure terminal of JMS to Error Queue where it put all the backed messages. when I deploy the flow it doesnt complains anything, But when the message comes from the Publisher , The flow error's out giving the below error

16:32:05 WebSphere Broker v6003: (WBRK6_DEFAULT_BROKER.TEST)[-1369519184]BIP2667E: An error occurred in node 'MSGFLOW.MQOutput' writing message to queue 'TEST_IN' on queue manager 'WBRK6_DEFAULT_QUEUE_MANAGER'. State = '-1' 'MQW102' '2019' '' : WBRK6_DEFAULT_BROKER.dc9a8f00-1501-0000-0080-f8f776c3daa5: /build/S600_P/src/DataFlowEngine/ImbMqOutputNode.cpp: 2142: ImbMqOutputNode::putMessage: ComIbmMQOutputNode: MSGFLOW#FCMComposite_1_5

I searched for the Error MQW102 which says Cannot write to target queue.I made the TEST_IN Output Queue Node property as "Default" and checked everything. But doesnt show anything.

Can anyone help me to say what exact problem is that referring to?
Is it good idea to configure failure terminal of JMSInput Node to a Error Q?

Thanks In Advance

-Learner
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Tue Sep 25, 2007 1:51 pm    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

That 2019 might be the MQRC.

Are you using a JMSInput and an MQOutput? Did you include the JMSMQTransform node?
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
jorro004
PostPosted: Tue Sep 25, 2007 1:54 pm    Post subject: Reply with quote

Acolyte

Joined: 25 Aug 2007
Posts: 50

Hi Jeff,

Here is my flow

JMSInput Node -- > JMSMQ Transform---> MQOutput---> Filter---> Compute -- MQOutput

I configured failure terminal of JMS to Error Q

Am I using the wrong nodes for my requirement?

Thanks
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Tue Sep 25, 2007 1:59 pm    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

To be clear...

JMSInput Node -->(failure terminal)-->JMSMQTransform-->...-->MQOutput

?

Every path that takes you From a JMSInput node TO an MQOutput node has to go THROUGH a JMSMQTransform node.

Also, you may want to use the Catch terminal, instead, and end the processing with a Throw node.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
jorro004
PostPosted: Tue Sep 25, 2007 2:27 pm    Post subject: Reply with quote

Acolyte

Joined: 25 Aug 2007
Posts: 50

JMSInput Node --> JMSMQ Transform --->MQOutput

The Out terminal of JMS is connected to JMSMQ Transform.
Failure terminal is connected to Error Q(MQOutput

Is it good idea to configure Out terminal to Error Q or else and Catch terminal to throw node?

And also what does the Error MQW102 mean?

Thanks
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Tue Sep 25, 2007 2:32 pm    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

Every path that leads from the JMSInput TO any MQOutput node needs to pass through an JMSMQTransform node.

So If you have Out terminal connected to one MQOutput node, and failure terminal connected to a DIFFERENT MQOutput node, then BOTH paths have to go to JMSMQTransforms.

MQW102, I don't know - what you said "can't write to the queue".
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
Kumar4
PostPosted: Thu Sep 27, 2007 2:14 pm    Post subject: Reply with quote

Apprentice

Joined: 12 Aug 2007
Posts: 27

Hi,

I have a question on the above discussion which relates to my problem.
I'm using a JMSInput for my flow which subsribes to message from a different application.

I would like to know about the failure messages, what happens to the message if it error's out in the middle of flow.?
How can that message be caught in any Output Node?

I configured JMS Failure terminal to the Error Q(MQOutput), where I can see the rolledback message. But the messageflow deosn't insert message to the errorq, It always send back to the published application.

Is there any way that I can catch all those rolledback messages in a exception queue using MQOutput node?

I know there is a backout Destination where these messages called be stored, But I need to catch them in my flow instead of publisher

Thanks
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 » Problem with JMSInput Node
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.