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 » Message flow with 2 input nodes causing 2026.

Post new topic  Reply to topic
 Message flow with 2 input nodes causing 2026. « View previous topic :: View next topic » 
Author Message
CHERIANV
PostPosted: Thu Jun 10, 2004 5:43 am    Post subject: Message flow with 2 input nodes causing 2026. Reply with quote

Apprentice

Joined: 15 Feb 2002
Posts: 43
Location: New York
Hi,
We have a flow running on a Z/OS broker , WMQI 2.1 /WMQ 5.3 . The flow has 2 input nodes each having its own input queue. There's only 1 instance of the flow deployed in the execution group but the transactions are of high volume since recently . Just recently during run-time I am seeing the following error messages (below) from the Broker log but the flow seems to be working fine. There are no messages stuck in the input queue or in any error queue as wverything is processing fine . I only see these error messages in the Broker logs. I wouldnt have known if there were any problems at all if I hadnt checked the logs. Any ideas on what could be the reason ? Am wondering if it is recommended for a flow to have 2 input nodes and if I could b getting this message for messages arriving at the queues at the same time or if it could be something else. Any input is appreciated ..Thanks in advance!


BIP2606E: Unable to get message from MQSeries queue 'queue name': MQCC=2; MQRC=2026; node 'nodename'. : BRKNAME.95b58f4b-ee00-0000-0080-f5c0200fcd82: /build/S210P/src/DataFlowEngine/ImbMqInputNode.cpp: 1084: ImbMqInputNode::readQueue: ComIbmMQInputNode: af43d265-f600-0000-0080-fb945ae2c18a
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Thu Jun 10, 2004 5:56 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981
Are you sure this isn't the same problem you have here: http://www.mqseries.net/phpBB2/viewtopic.php?t=15798?

Because the problem in that message appears to be an application outside your broker creating a bad message.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
CHERIANV
PostPosted: Thu Jun 10, 2004 6:32 am    Post subject: Reply with quote

Apprentice

Joined: 15 Feb 2002
Posts: 43
Location: New York
Jeff,
The 2026 reason code with my previous posting led me to beleive that the message which is really an acknowledgement message created by a remote application was not right. But this application has been sending the same acknowledgement message for over a year with no problems. All what hte input node that processes this message does it to discard it. Also, over the weekend these errors suddenly stopped after a Broker recycle. After a couple of days, it started again and that behavior is what is really puzzling . Also, if not for the logs there is nothing that indicates a problem as there are no messages stuck anywhere.

Cherian
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 » Message flow with 2 input nodes causing 2026.
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.