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 » mqsi error

Post new topic  Reply to topic
 mqsi error « View previous topic :: View next topic » 
Author Message
sandiksk
PostPosted: Fri Jul 08, 2005 1:08 am    Post subject: mqsi error Reply with quote

Centurion

Joined: 08 Jun 2005
Posts: 133

I am trying to do the procedure given in the redbook "Using WebSphere Business Integration Brokers Toolkit V5.02".
After creating the broker archive and deploying it(by draging the bar file into the execution group). It says in the book that, postcard and postcardMS must be visible in the default execution group. but i am not able to see it in the execution group. the deploy worked succesfully though

The alerts show
Execution group is not running.

The event log shows these errors
1)BIP2066E: Broker WBRK_BROKER (UUID 2c4e82f5-0401-0000-0080-8d5b1441ea49) was unable to retrieve an internal configuration response message for execution group 'default' within the 360 second Configuration Timeout.
The execution group did not respond within the Configuration Timeout period. A negative response is returned to the Configuration Manager for this execution group. The Configuration Timeout is the maximum length of time that an execution group is allowed to apply a deployed configuration change. By default the Configuration Timeout period is 300 seconds. You can increase (or decrease) the timeout by using the mqsichangebroker option, ConfigurationTimeout. This will not resolve any underlying problem with the deployed message, but can be used to reduce the response turnaround time or increase it to allow for large and complex deployments.

Investigate why the execution group was unable to respond before being timed out. Use the system log messages to determine if there is a problem with the execution group. You should check that your system is not running short of resources, for example, you may need to increase the WebSphere MQ log size. Reducing the complexity of the deploy by reducing the number of execution groups may also help to alleviate this problem. Correct the problem and redeploy the broker's configuration from the Message Brokers Toolkit. If there are no other failure diagnostics then you should consider increasing the Configuration Timeout, increase this value in units of 300 until this message no longer occurs. Contact your IBM support center if you are unable to resolve the problem.


2)BIP2087E: Broker WBRK_BROKER 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.


could anyone tell me what couls be the problem.
any kind of help will be appreciated as i am new to WMQSI
thanks in advance
Back to top
View user's profile Send private message
recallsunny
PostPosted: Fri Jul 08, 2005 5:38 am    Post subject: Reply with quote

Disciple

Joined: 15 Jun 2005
Posts: 163
Location: Massachusetts

You can change the 360 second Configuration Timeout value to a higher value using the mqsichangebroker command, Refer to your toolkit help contents.
However I suspect that should not have been causing the problem, as relatively simple flows don't take long to get deployed. Try doing the following before you change the broker properties.

Cancel all deployments by clicking on your domain root.
Restart your broker and try to deploy again.
If the problem persists you could try installing the latest CSD available.

BTW, wat's WMQSI ...
Back to top
View user's profile Send private message
sandiksk
PostPosted: Fri Jul 08, 2005 11:08 am    Post subject: cant see the workshop folder Reply with quote

Centurion

Joined: 08 Jun 2005
Posts: 133

thanks for the suggestion. I just stopped everything, restarted my laptop, and started everything. Suprisingly it worked.
This time i am having a new kind of problem
i am trying "Testing the message flow" part of the redbook. It says to open the postcard.enqueue file using the Enqueue editor.
i am not able see that file in the Resource navigator view. I am not sure how to open it.
In the Resource Navigator view i am not able to view the PostcardWorkshop folder. I guess the enqueue file will be in that folder.
can anyone tell me what could be the problem.
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 » mqsi error
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.