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 » need hardcore expert to fix broker issue

Post new topic  Reply to topic
 need hardcore expert to fix broker issue « View previous topic :: View next topic » 
Author Message
vikassalvi
PostPosted: Thu Nov 18, 2004 10:41 am    Post subject: need hardcore expert to fix broker issue Reply with quote

Newbie

Joined: 24 Sep 2003
Posts: 9
Hi,
We are getting some weird issue that no one is able to solve.
we have two broker on two different unix boxes and one config manager on windows server. we delpoyed same code on both brokers but one is not working correctly . there is no problem in code and it work in all other environment except prod.
when we delpoy everything come to green status and looks okay
but when we recyle the broker some of the message flows turns red
and here are the messages in see in the infosyslog.log
Nov 18 13:34:43 roc08650p032 WMQIv210[45868]: (MQIPB04.BXX_Claims_Status_835)[1]BIP2275E: Database record associated with mess
age flow '69913369-f700-0000-0080-fd9394c98087' is not valid. : MQIPB04.30faf748-0001-0000-0080-e85eab8a383b: /build/S210_P/sr
c/DataFlowEngine/ImbDataFlowDirector.cpp: 2291: ImbDataFlowDirector::loadAllDataFlowsFromDatabase: ExecutionGroup: 30faf748-00
01-0000-0080-e85eab8a383b
Nov 18 13:34:43 roc08650p032 WMQIv210[45868]: (MQIPB04.BXX_Claims_Status_835)[1]BIP5009E: XML Parsing Errors have occurred. :
MQIPB04.30faf748-0001-0000-0080-e85eab8a383b: /build/S210_P/src/MTI/MTIforBroker/GenXmlParser2/XmlImbParser.cpp: 409: XmlImbPa
rser::parseRightSibling: :
Nov 18 13:34:43 roc08650p032 WMQIv210[45868]: (MQIPB04.BXX_Claims_Status_835)[1]BIP5004E: XML parsing error (The attribute 'va
lidateMaster' is already used in element 'ComIbmMQOutputNode') encountered on line 9064 column 87 while parsing element Messag
eFlow. : MQIPB04.30faf748-0001-0000-0080-e85eab8a383b: /build/S210_P/src/MTI/MTIforBroker/GenXmlParser2/XmlBrokerAsgardParser.
cpp: 762: XmlBrokerAsgardParser::error: :
Nov 18 13:34:44 roc08650p032 WMQIv210[45868]: (MQIPB04.BXX_Claims_Status_835)[1]BIP2275E: Database record associated with mess
age flow '84740369-f700-0000-0080-fd9394c98087' is not valid. : MQIPB04.30faf748-0001-0000-0080-e85eab8a383b: /build/S210_P/sr
c/DataFlowEngine/ImbDataFlowDirector.cpp: 2291: ImbDataFlowDirector::loadAllDataFlowsFromDatabase: ExecutionGroup: 30faf748-00
01-0000-0080-e85eab8a383b
Nov 18 13:34:44 roc08650p032 WMQIv210[45868]: (MQIPB04.BXX_Claims_Status_835)[1]BIP5009E: XML Parsing Errors have occurred. :
MQIPB04.30faf748-0001-0000-0080-e85eab8a383b: /build/S210_P/src/MTI/MTIforBroker/GenXmlParser2/XmlImbParser.cpp: 409: XmlImbPa
rser::parseRightSibling: :
Nov 18 13:34:44 roc08650p032 WMQIv210[45868]: (MQIPB04.BXX_Claims_Status_835)[1]BIP5004E: XML parsing error (Expected equal si
gn) encountered on line 2985 column 448 while parsing element MessageFlow. : MQIPB04.30faf748-0001-0000-0080-e85eab8a383b: /bu
ild/S210_P/src/MTI/MTIforBroker/GenXmlParser2/XmlBrokerAsgardParser.cpp: 762: XmlBrokerAsgardParser::error: :
Nov 18 13:34:45 roc08650p032 WMQIv210[45868]: (MQIPB04.BXX_Claims_Status_835)[1]BIP2275E: Database record associated with mess
age flow '8d8e655f-fb00-0000-0080-d2f124297fa3' is not valid. : MQIPB04.30faf748-0001-0000-0080-e85eab8a383b: /build/S210_P/sr
c/DataFlowEngine/ImbDataFlowDirector.cpp: 2291: ImbDataFlowDirector::loadAllDataFlowsFromDatabase: ExecutionGroup: 30faf748-00
01-0000-0080-e85eab8a383b
Nov 18 13:34:45 roc08650p032 WMQIv210[45868]: (MQIPB04.BXX_Claims_Status_835)[1]BIP5009E: XML Parsing Errors have occurred. :
MQIPB04.30faf748-0001-0000-0080-e85eab8a383b: /build/S210_P/src/MTI/MTIforBroker/GenXmlParser2/XmlImbParser.cpp: 409: XmlImbPa
rser::parseRightSibling: :
Nov 18 13:34:45 roc08650p032 WMQIv210[45868]: (MQIPB04.BXX_Claims_Status_835)[1]BIP5004E: XML parsing error (The attribute 'us
erTraceLevel' is already used in element 'ComIbmComputeNode') encountered on line 7668 column 93 while parsing element Message
Flow. : MQIPB04.30faf748-0001-0000-0080-e85eab8a383b: /build/S210_P/src/MTI/MTIforBroker/GenXmlParser2/XmlBrokerAsgardParser.c
pp: 762: XmlBrokerAsgardParser::error: :
Back to top
View user's profile Send private message
mayur2378
PostPosted: Thu Nov 18, 2004 12:26 pm    Post subject: Reply with quote

Apprentice

Joined: 26 May 2004
Posts: 47
Hey Vikas

Have you tried recreating your broker. From the log i can see some problems with the UUID.

Mayur
Back to top
View user's profile Send private message Yahoo Messenger
kirani
PostPosted: Thu Nov 18, 2004 12:28 pm    Post subject: Reply with quote

Jedi Knight

Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
Do all these machines have same version of MQSI/WMQI/WBIMB (and CSD) installed? Please provide your environment details.
_________________
Kiran


IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries

Back to top
View user's profile Send private message Visit poster's website
vikassalvi
PostPosted: Thu Nov 18, 2004 1:09 pm    Post subject: we tried all these steps Reply with quote

Newbie

Joined: 24 Sep 2003
Posts: 9
we have same CSD , OS patch level across non-prod and prod env
we recreated broker 3 times and re delpoyed the code
Strange thing is if you deploy everything looks green only problem come when you restart the broker some message flows goes in red status
so anything correpting

vikas
Back to top
View user's profile Send private message
vikassalvi
PostPosted: Thu Nov 18, 2004 1:22 pm    Post subject: we tried all these steps Reply with quote

Newbie

Joined: 24 Sep 2003
Posts: 9
we have same CSD , OS patch level across non-prod and prod env
we recreated broker 3 times and re delpoyed the code
Strange thing is if you deploy everything looks green only problem come when you restart the broker some message flows goes in red status
so anything correpting

vikas
Back to top
View user's profile Send private message
vikassalvi
PostPosted: Thu Nov 18, 2004 1:36 pm    Post subject: here my environment details Reply with quote

Newbie

Joined: 24 Sep 2003
Posts: 9
Production enviromnet
1) two unix broker boxes
os : IBM AIX
oslevel : 5.1.0.0
MQ : 5.3
CSD : 06
WMQI : 2.1
CSD : 06
DB2 : 7.2 CSD 4
2) WINDOWS 2000 SERVER for config manager
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Thu Nov 18, 2004 1:37 pm    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981
Is the problem specific to a single broker, specific to a single set of message flows, or random?
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
kirani
PostPosted: Thu Nov 18, 2004 2:44 pm    Post subject: Reply with quote

Jedi Knight

Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
Try doing a complete deploy of all of your Execution Groups once before restarting the Broker. I hope no one has played with internal broker DB.
_________________
Kiran


IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries

Back to top
View user's profile Send private message Visit poster's website
vikassalvi
PostPosted: Thu Nov 18, 2004 4:34 pm    Post subject: that's strange Reply with quote

Newbie

Joined: 24 Sep 2003
Posts: 9
if we do a complete deploy on broker. everything comes fine and all message flows looks green but if you restart next time then some of them goes in red status and if you do again deploy everything become green and this is only happening for one broker
Back to top
View user's profile Send private message
kirani
PostPosted: Thu Nov 18, 2004 5:25 pm    Post subject: Reply with quote

Jedi Knight

Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
I think you should open a PMR for this problem.
_________________
Kiran


IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries

Back to top
View user's profile Send private message Visit poster's website
jefflowrey
PostPosted: Thu Nov 18, 2004 5:37 pm    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981
How are you restarting?

If you do not do a clean shutdown (mqsistop gives back a good response), you can end up leaving bad rows in the broker table.

But yes, open a PMR.

Or hire a consultant....
_________________
I am *not* the model of the modern major general.
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 » need hardcore expert to fix broker issue
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.