|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
WMB 6 - Unable to create 64 bit execution group in broker |
« View previous topic :: View next topic » |
Author |
Message
|
sanu_mit |
Posted: Fri May 09, 2008 5:18 am Post subject: WMB 6 - Unable to create 64 bit execution group in broker |
|
|
Apprentice
Joined: 03 Jul 2003 Posts: 25 Location: Kolkata
|
My environment is as follows: -
System - AIX
DB2 - 64 bit instance - DB2/AIX64 8.2.7
WMQ - 6.0.2.1
WMB - 6.0.0.6
I have successfully created the broker, 32 bit execution groups and deployed message flows in it. But when I create a 64 bit execution group in the broker and try to deploy a message flow it gives the following error message: -
BIP2066E: Broker MB6_BROKER01_64 (UUID ca49bbcd-1901-0000-0080-b64d1b1d4103) was unable to retrieve an internal configuration response message for execution group 'default_64bit' 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 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, mqsideploy command or Config Manager Proxy. 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.
Also the environment settings are as follows: -
_=/usr/bin/env
MANPATH=/usr/share/man:/usr/local/man:/usr/dt/man:/opt/freeware/man:
LANG=C
PATH=/opt/IBM/mqsi/6.0/jre/bin:/opt/IBM/mqsi/6.0/bin:/usr/local/bin:/home/wmbuser/bin:/home/wmbuser/sbin:/usr/bin:/etc:/usr/sbin:/usr/ucb:/usr/bin/X11:/sbin:/usr/java14/jre/bin:/usr/java14/bin:/usr/bin:/etc:/usr/sbin:/usr/ucb:/usr/bin/X11:/sbin:.:/home/db2inst1/sqllib/bin:/home/db2inst1/sqllib/adm:/home/db2inst1/sqllib/misc
MQSI_JARPATH=/opt/IBM/mqsi/6.0/classes:/opt/IBM/mqsi/6.0/messages
LC__FASTMSG=true
MQSI_REGISTRY=/var/mqsi
CLASSPATH=/opt/IBM/mqsi/6.0/classes/derby.jar:/opt/IBM/mqsi/6.0/classes/ConfigManagerProxy.jar:/opt/IBM/mqsi/6.0/classes/configutil.jar:/usr/mqm/java/lib/com.ibm.mq.jar:/usr/mqm/java/lib/connector.jar:/opt/IBM/mqsi/6.0/messages:/home/db2inst1/sqllib/java/db2java.zip:/home/db2inst1/sqllib/java/db2jcc.jar:/home/db2inst1/sqllib/function:/home/db2inst1/sqllib/java/db2jcc_license_cisuz.jar:/home/db2inst1/sqllib/java/db2jcc_license_cu.jar:.
MQSI_FAD=3
DISTHUB_PATH=/opt/IBM/mqsi/6.0
MQSI_LILPATH=/opt/IBM/mqsi/6.0/lil:/opt/IBM/mqsi/6.0/jplugin
LOCPATH=/usr/lib/nls/loc
VWSPATH=/home/db2inst1/sqllib
MQSI_JREPATH=/opt/IBM/mqsi/6.0/jre
MQSI_DEVELOPMENT=/var/mqsi/registry
LDR_CNTRL=USERREGS
AUTHSTATE=files
MQSI_LILPATH64=/opt/IBM/mqsi/6.0/lil64:/opt/IBM/mqsi/6.0/jplugin
MQSI_VERSION=6.0.0.6
MQSI_CATALINA_HOME=/opt/IBM/mqsi/6.0/catalina
SHELL=/usr/bin/ksh
ODMDIR=/etc/objrepos
MQSI_FILEPATH=/opt/IBM/mqsi/6.0
ODBCINI=/var/mqsi/odbc/.odbc.ini
MQSI_LIBPATH64=/opt/IBM/mqsi/6.0/jre/ppc64/bin:/opt/IBM/mqsi/6.0/jre/ppc64/bin/classic:/usr/mqm/lib64:/opt/IBM/mqsi/6.0/DD64/lib:/opt/IBM/mqsi/6.0/xml4c/lib64
MQSI_VERSION_F=6
ODBCINI64=/var/mqsi/odbc/odbc64.ini
MQSI_WORKPATH=/var/mqsi
DB2INSTANCE=db2inst1
MQSI_EXMLTCONFIGPATH=/opt/IBM/mqsi/6.0/exmltConfig
MQSI_VERSION_M=0
MQSI_VERSION_V=6
MQSI_VERSION_R=0
NLSPATH=/opt/IBM/mqsi/6.0/messages/%L/%N:/opt/IBM/mqsi/6.0/messages/En_US/%N:/usr/lib/nls/msg/%L/%N:/usr/lib/nls/msg/%L/%N.cat
LIBPATH=/home/db2inst1/sqllib/lib32:/opt/IBM/mqsi/6.0/jre/bin:/opt/IBM/mqsi/6.0/jre/bin/classic:/usr/mqm/java/lib:/opt/IBM/mqsi/6.0/lib:/opt/IBM/mqsi/6.0/bin:/opt/IBM/mqsi/6.0/merant/lib:/opt/IBM/mqsi/6.0/xml4c/lib:/usr/lib:/lib:/home/db2inst1/sqllib/lib
LD_LIBRARY_PATH=/home/db2inst1/sqllib/lib
Any help in this regard is highly appreciated.
Thanks in anticipation.
Sanu. |
|
Back to top |
|
 |
Gaya3 |
Posted: Fri May 09, 2008 5:41 am Post subject: |
|
|
 Jedi
Joined: 12 Sep 2006 Posts: 2493 Location: Boston, US
|
check the broker logs,
and check if the broker abends ? If so raise a PMR
Regards
Gayathri _________________ Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
Back to top |
|
 |
mvarghese |
Posted: Sat May 10, 2008 4:09 am Post subject: |
|
|
Centurion
Joined: 27 Sep 2006 Posts: 141
|
Try to Change the ODBCINI with path of .odbc64.ini file and its necessary entries depends on your confugurations..make sure this file copied from right location as IBM pointed in docs...
Other way is to Install 6.1 Broker..everything will works fine..
Also do check your db2 instance , is it created 64 bit or not.
db2ilist -a _________________ Jain Varghese |
|
Back to top |
|
 |
|
|
 |
|
Page 1 of 1 |
|
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
|
|
|
|