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 » Deployment errors

Post new topic  Reply to topic Goto page Previous  1, 2
 Deployment errors « View previous topic :: View next topic » 
Author Message
mqwbiwf
PostPosted: Thu Mar 22, 2007 8:42 am    Post subject: Reply with quote

Centurion

Joined: 21 Jul 2006
Posts: 126

when i tried the 'resubscribe to status topics' , it still throws errors in broker logs:

Mar 22 11:27:59 wbintgtst06 user:info WebSphere Broker v6003[1376434]: (ConfigMgr )[3342]BIP1536S: The Configuration Manager was unable to register for internal subscriptions with broker WSUGTS001 . : ConfigMgr .agent: /build/S600_P/src/DataFlowEngine/NativeTrace/ImbNativeTrace.cpp: 686: BrokerManager.resolveRegSub: ConfigMgr : ConfigMgr

Mar 22 11:27:59 wbintgtst06 user:info WebSphere Broker v6003[1376434]: (ConfigMgr )[3342]BIP2087E: Broker WSUGTS001 was unable to process the internal configuration message. : ConfigMgr .agent: /build/S600_P/src/DataFlowEngine/NativeTrace/ImbNativeTrace.cpp: 711: BrokerManager.logLogEntry: ConfigMgr : ConfigMgr

Mar 22 11:27:59 wbintgtst06 user:info WebSphere Broker v6003[1376434]: (ConfigMgr )[3342]BIP2064I: Broker WSUGTS001 (UUID 3c62e1af-0e01-0000-0080-91c6fd623b99) Execution Group 'TESTEG1' (UUID 32d14c2a-0f01-0000-0080-b262ce326b3f), deployed configuration message rejected. : ConfigMgr .agent: /build/S600_P/src/DataFlowEngine/NativeTrace/ImbNativeTrace.cpp: 711: BrokerManager.logLogEntry: ConfigMgr : ConfigMgr

Mar 22 11:27:59 wbintgtst06 user:info WebSphere Broker v6003[1376434]: (ConfigMgr )[3342]BIP2062E: Broker WSUGTS001 (UUID 3c62e1af-0e01-0000-0080-91c6fd623b99) execution group '' (UUID 578faa50-1001-0000-0080-eef2af127c39) detected that the deployed configuration message received contained an invalid XML tag. : ConfigMgr .agent: /build/S600_P/src/DataFlowEngine/NativeTrace/ImbNativeTrace.cpp: 711: BrokerManager.logLogEntry: ConfigMgr : ConfigMgr

Mar 22 11:27:59 wbintgtst06 user:info WebSphere Broker v6003[1376434]: (ConfigMgr)[3342]BIP2064I: Broker WSUGTS001 (UUID 3c62e1af-0e01-0000-0080-91c6fd623b99) Execution Group '$SYS_mqsi' (UUID 82a6e590-12b3-11d3-81a2-00203506a68e), deployed configuration message rejected. : ConfigMgr.agent: /build/S600_P/src/DataFlowEngine/NativeTrace/ImbNativeTrace.cpp: 711: BrokerManager.logLogEntry: ConfigMgr: ConfigMgr




btw, i do see the system exec grp "SYS_mqsi" in broker log, but not in the toolkit. so, is this also a rouge (phantom) exec grp? should i delete it from the brokeraaeg table? i would really like to see this issue solved without recreating the broker, and would be greatly appreciated if you guys can help me out!
Back to top
View user's profile Send private message
mqmatt
PostPosted: Thu Mar 22, 2007 9:43 am    Post subject: Reply with quote

Grand Master

Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK

Please raise a PMR.
Back to top
View user's profile Send private message
dertel
PostPosted: Mon Apr 23, 2007 11:35 am    Post subject: Reply with quote

Novice

Joined: 17 Dec 2003
Posts: 15

I've just started having the same errors as those described in this post.

Broker and configuration manager are both running on the same z/linux server; maintenance level is 6.0.0.3. Both are running as userid wmqi.

In response to a phantom execution group problem, I deleted the corresponding row from BROKERAAEG. MQSILIST and toolkit displays are now both consistent and show what I'd expect.

However, I'm now seeing BIP1536S when deploying from the toolkit. Broker log shows the BIP1536S message and also shows BIP2087E, BIP2064I, and BIP2062E. I also see all of these messages on the broker log when I deploy from the command line.

Problem seemingly started in response to deleting the row from BROKERAAEG.
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Mon Apr 23, 2007 1:11 pm    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20763
Location: LI,NY

dertel wrote:
I've just started having the same errors as those described in this post.

Broker and configuration manager are both running on the same z/linux server; maintenance level is 6.0.0.3. Both are running as userid wmqi.

In response to a phantom execution group problem, I deleted the corresponding row from BROKERAAEG. MQSILIST and toolkit displays are now both consistent and show what I'd expect.

However, I'm now seeing BIP1536S when deploying from the toolkit. Broker log shows the BIP1536S message and also shows BIP2087E, BIP2064I, and BIP2062E. I also see all of these messages on the broker log when I deploy from the command line.

Problem seemingly started in response to deleting the row from BROKERAAEG.

You're not supposed to delete the row. You're supposed to change the status field on that row... (Use the Search button and find previous post). Now you might have to do a full deploy...of the topology...

Enjoy
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
Display posts from previous:   
Post new topic  Reply to topic Goto page Previous  1, 2 Page 2 of 2

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Deployment errors
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.