| Author |
Message
|
| samgunddi |
 Posted: Mon Feb 07, 2005 1:05 pm Post subject: [Solved] Message Broker error BIP2203E: An execution group |
 |
|
Acolyte
Joined: 17 May 2004
Posts: 54
|
Hi gurus,
Problem starting the broker.
MQSIv500[3396]: [ID 702911 user.error] (WBRKBK.$SYS_mqsi)[1]BIP2203E: An execution group has encountered a problem whilst starting. : WBRKBK.82A6E590-12B3-11D3-81A2-00203506A68E: /build/S500_P/src/DataFlowEngine/ImbMain.cpp: 570: main: :
Environment:
Broker V5 CSD04 (Sun 8, MQ 5.3 CSD04, DB2 8.1 FP2)
ConfigMgr V5 CSD04 (Win 2000 Server SP4, MQ 5.3 CSD04, DB2 8.1 FP2)
Toolkit V5 CSD04 (Win 2000 SP4, MQ 5.3 CSD04, DB2 8.1 FP2)
This problem occured at start command after i reinstalled the problem for testing. Checked all the prereqs; Increases the ConfigurationTimeOut to 1000 as indicated by the ConfigMgr event log. EG never start, the error occurs until ConfigurationTimeOut.
Any help would be appreciated.
Thanks in Adv, AJ
Last edited by samgunddi on Tue Feb 08, 2005 12:16 pm; edited 1 time in total |
|
| Back to top |
|
 |
| JT |
| Posted: Mon Feb 07, 2005 1:10 pm Post subject: |
|
|
Padawan
Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.
|
| Quote: |
| MQSIv500[3396]: [ID 702911 user.error] (WBRKBK.$SYS_mqsi)[1]BIP2203E: An execution group has encountered a problem whilst starting. : WBRKBK.82A6E590-12B3-11D3-81A2-00203506A68E: /build/S500_P/src/DataFlowEngine/ImbMain.cpp: 570: main: : |
There should be additional messages that accompany this one. Share them. |
|
| Back to top |
|
|
| samgunddi |
| Posted: Mon Feb 07, 2005 1:19 pm Post subject: |
|
|
Acolyte
Joined: 17 May 2004
Posts: 54
|
JT, the event log of configmgr.
Event Type: Error
Event Source: BIPv500
Event Category: None
Event ID: 1536
Description:
( ConfigMgr ) Configuration Manager unable to register for internal subscriptions with broker WBRKBK.
Although the preceding deploy operation was successful, a subsequent attempt by the Configuration Manager to register for internal subscriptions with broker WBRKBK was not successful. This means that the Message Brokers Toolkit may not reliably show the correct status of the resources assigned to broker WBRKBK. 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.
Event Type: Error
Event Source: BIPv500
Event Category: None
Event ID: 2066
Description:
( ConfigMgr ) Broker WBRKBK (UUID fd9152ed-0101-0000-0080-e148cef4a83b) was unable to retrieve an internal configuration response message for execution group '$SYS_mqsi' 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 Business Integration 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.
Event Type: Error
Event Source: BIPv500
Event Category: None
Event ID: 1536
Description:
( ConfigMgr ) Configuration Manager unable to register for internal subscriptions with broker WBRKBK.
Although the preceding deploy operation was successful, a subsequent attempt by the Configuration Manager to register for internal subscriptions with broker WBRKBK was not successful. This means that the Message Brokers Toolkit may not reliably show the correct status of the resources assigned to broker WBRKBK. 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. |
|
| Back to top |
|
|
| JT |
| Posted: Mon Feb 07, 2005 1:26 pm Post subject: |
|
|
Padawan
Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.
|
| Quote: |
| MQSIv500[3396]: [ID 702911 user.error] (WBRKBK.$SYS_mqsi)[1]BIP2203E: An execution group has encountered a problem whilst starting. : WBRKBK.82A6E590-12B3-11D3-81A2-00203506A68E: /build/S500_P/src/DataFlowEngine/ImbMain.cpp: 570: main: : |
Isn't this message from the system log on the broker server? There should be some qualifying messages that identify the error event. |
|
| Back to top |
|
|
| samgunddi |
| Posted: Mon Feb 07, 2005 1:45 pm Post subject: |
|
|
Acolyte
Joined: 17 May 2004
Posts: 54
|
[quote]
Isn't this message from the system log on the broker server?
yes
Other than, BIP1536S, BIP2066E, BIP2087E in toolkit do not see any other recorded error events (unless i am missing something). |
|
| Back to top |
|
|
| JT |
| Posted: Mon Feb 07, 2005 1:57 pm Post subject: |
|
|
Padawan
Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.
|
Okay, no messages.
Was an abend file generated (/var/mqsi/errors/)? |
|
| Back to top |
|
|
| samgunddi |
| Posted: Mon Feb 07, 2005 2:00 pm Post subject: |
|
|
Acolyte
Joined: 17 May 2004
Posts: 54
|
| /var/mqsi/errors is Empty |
|
| Back to top |
|
|
| shra_k |
| Posted: Tue Feb 08, 2005 3:00 am Post subject: |
|
|
Apprentice
Joined: 30 Dec 2002
Posts: 37
|
The errors reported are generic in nature. The $SYS_mqsi shows that this is a new broker and it fails to startup. I believe u have not done any tolopgy deploy on this.
This failure could be because of many reasons ..few like...wrong JRE level..Environment not setup properly or it could be that you might have not run the sample profile supplied or it could be becuase u have missed out some step in the setup (like mqsisetupdatabase).....
Because of any of the above reasons the startup might fail and throw the generic erros that u have shared with us.
Its just an environment issue, please cross check with the manuals whether u have done everything correctly or not. |
|
| Back to top |
|
|
| samgunddi |
| Posted: Tue Feb 08, 2005 7:04 am Post subject: |
|
|
Acolyte
Joined: 17 May 2004
Posts: 54
|
| Quote: |
| The errors reported are generic in nature. The $SYS_mqsi shows that this is a new broker and it fails to startup. I believe u have not done any tolopgy deploy on this. |
Yes, it is a new broker
| Quote: |
| ..wrong JRE level.. |
Broker:
$ java -version java version "1.3.1_12"
ConfigMgr:
java -version java version "1.4.0"
Toolkit:
java -version java version "1.4.0"
| Quote: |
| Environment not setup properly or it could be that you might have not run the sample profile supplied or it could be becuase u have missed out some step in the setup (like mqsisetupdatabase)..... |
I am invoking both the profile.sol and db2profile.
mqsi_setupdatabase is completed
$ pwd
/var/wmqi/lib
$ ls -al libdb2.so
lrwxrwxrwx 1 bin mqbrkrs 31 Feb 4 17:03 libdb2.so -> /opt/IBM/db2/V8.1/lib/libdb2.so
.odbc.ini
[ODBC Data Sources]
WBRKBKDB=IBM DB2 ODBC Driver
WBRKCMDB=IBM DB2 ODBC Driver
RESERVDB=IBM DB2 ODBC Driver
[WBRKBKDB]
Driver=/clocal/udb/srvr7300/sqllib/lib/libdb2.so
Description=WBRKBKDB DB2 ODBC Database
Database=WBRKBKDB
[WBRKCMDB]
Driver=/clocal/udb/srvr7300/sqllib/lib/libdb2.so
Description=WBRKCMDB DB2 ODBC Database
Database=WBRKCMDB
[RESERVDB]
Driver=/clocal/udb/srvr7300/sqllib/lib/libdb2.so
Description=RESERVDB DB2 ODBC Database
Database=RESERVDB
[ODBC]
Trace=0
TraceFile=/var/wmqi/odbc/odbctrace.out
TraceDll=/opt/wmqi/merant/lib/odbctrac.so
InstallDir=/opt/wmqi/merant
Installation dir is different form the defult dir, i hope this is not causing any problems??
| Quote: |
http://publib.boulder.ibm.com/infocenter/wbihelp/index.jsp
Preparing the file system on UNIX systems
You can create a new directory anywhere on your system that has sufficient space for the product, and create a symbolic link from /opt/mqsi to that new directory. For example:
mkdir -p /bigdisk/mqsi
ln -s /bigdisk/mqsi /opt/mqsi
|
$ ls -al /opt/mqsi
lrwxrwxrwx 1 mqm mqbrkrs 32 Feb 4 16:09 /opt/mqsi -> /bigdisk/opt
$ ls -al /var/mqsi
lrwxrwxrwx 1 bin mqbrkrs 32 Feb 4 16:10 /var/mqsi -> /bigdisk/var[/code] |
|
| Back to top |
|
|
| JT |
| Posted: Tue Feb 08, 2005 7:25 am Post subject: |
|
|
Padawan
Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.
|
| Quote: |
| I am invoking both the profile.sol and db2profile |
Post the contents of the broker .profile. |
|
| Back to top |
|
|
| samgunddi |
| Posted: Tue Feb 08, 2005 7:32 am Post subject: |
|
|
Acolyte
Joined: 17 May 2004
Posts: 54
|
$ cat .profile
# @(#)local.profile 1.8 99/03/26 SMI
stty istrip
PATH=/usr/bin:/usr/ucb:/etc:/opt/mqm/samp/bin:.
export PATH
#-------------------------------------------------
if [ -f /instance home/sqllib/db2profile]; then
. /instance home/sqllib/db2profile
fi
if [ -f /bigdisk/mqsiprofile ]; then
. /bigdisk/profile.sol
fi
Both db2profile and profile.sol and vendor(IBM) provide files. |
|
| Back to top |
|
|
| samgunddi |
| Posted: Tue Feb 08, 2005 12:22 pm Post subject: |
|
|
Acolyte
Joined: 17 May 2004
Posts: 54
|
The message broker packages were not added during the installation. After reinstall it worked fine.
--during the custom installation process
| Quote: |
./setupsolaris -console -is:javaconsole
Please select the components you wish to install.
Please select from the following components:
[X] 1 - Broker
[X ] 2 - User Name Server
[ X] 3 - Message Broker Extensions
To select a choice enter its number, or 0 when you are finished [0]:
|
Notice the three option Broker, User Name Server and Message Broker Extensions; this is quite miss leading. Option 3 points towards WBI MB Rules and Formatter Extension. And option 1 - Broker only installs the Event Broker.
Thanks every one for all your help. |
|
| Back to top |
|
|
| ydsk |
| Posted: Fri Dec 30, 2005 10:23 am Post subject: |
|
|
Chevalier
Joined: 23 May 2005
Posts: 410
|
Hi,
How do I create the .profile file for a user ? WMBv6 was already installed on a AIX box, which already has WMQv5.3. A qmgr was built already. The service user id for broker is mqsiadm and its home directory was set to /opt/app/mqsiadm. I did an "ls -al" but I don't find the .profile file in the directory. Can someone please help ?
Thanks.
ydsk. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Dec 30, 2005 10:25 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
touch ~/.profile
vi ~/.profile
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
