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 » WBIMB deployment issues...

Post new topic  Reply to topic
 WBIMB deployment issues... « View previous topic :: View next topic » 
Author Message
waugh
PostPosted: Thu Feb 26, 2004 1:28 pm    Post subject: WBIMB deployment issues... Reply with quote

Master

Joined: 19 Feb 2004
Posts: 225

BROKER, CONFIGURATION MANAGER BOTH ARE ON WINDOWS...

i also tried solutions from earlier postings on this site, @@@

http://www.mqseries.net/phpBB2/viewtopic.php?t=3488

I AM GETTING FOLLOWING ERROR MESSAGES ALONG WITH

execution group not running Alert!!! when i deploy the broker topology..
it looked like permissions issue initially, i checked everything and looks fine...

-------------------------------------------------

BIP2045E: Broker HHARDOB01 (UUID 03f2ebf2-fa00-0000-0080-b481c3768d8b) running on WebSphere MQ queue manager HHARDNQ01 could not process an internal configuration message because the broker identity received in the message (UUID 572635f3-fa00-0000-0080-b481c3768d8b) did not match that of this broker.

An internal configuration message could not be processed and was rejected. Each broker is identified by a universally unique identifier called a UUID which is allocated when the user creates a definition for the broker. The configuration message received contained a broker UUID (572635f3-fa00-0000-0080-b481c3768d8b) that does not match the UUID of broker HHARDOB01 running on WebSphere MQ queue manager HHARDNQ01. There are two possible reasons for this. Either a user has accidentally specified queue manager HHARDNQ01 when defining another broker so that messages destined for the other broker have arrived at this broker, or the definition for broker HHARDOB01 was deleted and recreated on the Message Brokers Toolkit which has the effect of giving broker HHARDOB01 a new, different UUID.

-----------------------------------------------------------------

BIP2087E: Broker HHARDOB01 was unable to process the internal configuration message.

The entire internal configuration message failed to be processed successfully.

The internal configuration message failed to be processed, use the messages following this message to determine the reasons for the failure.

---------------------------------------------------------------

BIP1536S: Configuration Manager unable to register for internal subscriptions with broker HHARDOB01.

Although the preceding deploy operation was successful, a subsequent attempt by the Configuration Manager to register for internal subscriptions with broker was not successful. This means that the Message Brokers Toolkit may not reliably show the correct status of the resources assigned to broker HHARDOB01. The Configuration Manager also writes this message to the system event log, accompanied by other messages giving details of the problem.

Look at the messages for this problem in the system event log. Determine and correct the cause of the problem before attempting to deploy to this broker again. If this problem persists, contact your IBM support center.

-----------------------------

any idea? where it went wrong?

thanks in advance.....
Back to top
View user's profile Send private message
waugh
PostPosted: Thu Feb 26, 2004 1:41 pm    Post subject: Reply with quote

Master

Joined: 19 Feb 2004
Posts: 225

BIP2045E: Broker HHARDBK (UUID 8626adf3-fa00-0000-0080-b481c3768d8b) running on WebSphere MQ queue manager HHARDBK could not process an internal configuration message because the broker identity received in the message (UUID 8aefb2f3-fa00-0000-0080-b481c3768d8b) did not match that of this broker.

above is from a brand new configuration, you can ignore that part in earlier message...

the entries i can see in CBROKER table in the database are:::

8aefb2f3-fa00-0000-0080-b481c3768d8b
8aefb2f3-fa00-0000-0080-b481c3768d8b

in CUUID column

hope this helps a little bit...
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Thu Feb 26, 2004 1:47 pm    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

Drop and recreate the broker.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
waugh
PostPosted: Fri Feb 27, 2004 9:29 am    Post subject: Reply with quote

Master

Joined: 19 Feb 2004
Posts: 225

I did that several times, dropped broker, even databases, couple of times queue managers and recreated all of them... still gives me same error... IBM suggested to go back from java 1.4 to java 1.3.1.. didnt help...
Back to top
View user's profile Send private message
waugh
PostPosted: Fri Feb 27, 2004 9:43 am    Post subject: Reply with quote

Master

Joined: 19 Feb 2004
Posts: 225

Thanks Jeff,

I do not see any of the above error messages now...

but, it still says that the execution group is not running. an alert..

any idea?

i can see the deployed execution group and broker in database tables.

message in system application log:

( HHARDBK.$SYS_mqsi ) Execution Group started: process '3332'; thread '3352'; additional information: brokerName 'HHARDBK'; executionGroupUUID '82A6E590-12B3-11D3-81A2-00203506A68E'; executionGroupLabel '$SYS_mqsi'; defaultExecutionGroup 'true'; queueManagerName 'HHARDNQ01'; trusted 'false'; dataSourceName 'HHDABKDB'; userId 'mqsi1'; migrationNeeded 'false'; brokerUUID '1d9c03f8-fa00-0000-0080-b481c3768d8b'; filePath 'C:/Program Files/IBM/WebSphere Business Integration Message Brokers'; workPath 'C:/Program Files/IBM/WebSphere Business Integration Message Brokers'.

The execution Group has started using process '3332' and thread '3352' and will now start processing messages.

No user action required.

messages in workbench error log:

BIP4045I: Configuration changed successfully.

The message broker received a configuration message and updated its configuration accordingly. This change concerned its publish-subscribe capability.

No user action required.

--------------------------------------------------------------------

BIP2056I: Broker HHARDBK successfully processed the entire internal configuration message.

An internal configuration message was processed to completion.

No user action required.
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Sat Feb 28, 2004 12:33 pm    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

In WBIMB v5, execution groups do not start until something is deployed to them.
_________________
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 » WBIMB deployment issues...
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.