| Author |
Message
|
| bdrummond |
 Posted: Mon Jul 04, 2005 2:54 am Post subject: Unable to create Broker |
 |
|
Disciple
Joined: 06 May 2004
Posts: 164
|
Hi,
I am trying to create a second broker (Solaris machine) within the Message Brokers Toolkit (windows).
However, I am receiving the following error:
BIP1776S: Unexpected exception in the Configuration Manager ACLGroupEntry class execSysCommand method; exception text: 'java.io.IOException: CreateProcess: strmqm "CMGRQM1" error=5', 'CreateProcess: strmqm "CMGRQM1" error=5'.
While attempting a database operation on the configuration repository, an exception was caught by the Configuration Manager ACLGroupEntry class execSysCommand method. The database operation did not complete successfully. The exception text is: java.io.IOException: CreateProcess: strmqm "CMGRQM1" error=5, CreateProcess: strmqm "CMGRQM1" error=5.
The exception text may indicate that the DB2 JDBC Driver could be found; check that the system CLASSPATH variable contains access to the DB2 runtime classes. If the DB2 classes are present in the CLASSPATH or if the exception text indicates a different problem, please contact your IBM support center.
Does anyone know what the problem could be..?
Cheers. |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Mon Jul 04, 2005 4:41 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Looks like the process was unable to start qmgr CMGRQM1.
Have you tried starting it manually ?
Is there a problem with this qmgr ? Does it exist at all ?
Enjoy  |
|
| Back to top |
|
|
| bdrummond |
| Posted: Mon Jul 04, 2005 5:11 am Post subject: |
|
|
Disciple
Joined: 06 May 2004
Posts: 164
|
The QMgr is running and so is the ConfigMgr. I have stopped and restarted both of these but to no avail.  |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Jul 04, 2005 1:12 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| Could it be that the path variable in the user profile running the broker startup is not initialized correctly ? / not right group/ not right permissions ? |
|
| Back to top |
|
|
| chenulu |
| Posted: Mon Jul 04, 2005 5:22 pm Post subject: |
|
|
Voyager
Joined: 27 Mar 2002
Posts: 87
Location: Research Triangle Park, NC
|
Hi,
What is your CLASSPATH set to? Make sure you have db2java.zip and db2cc.jar in the CLASSPATH.
Regards, Chenulu |
|
| Back to top |
|
|
| bdrummond |
| Posted: Tue Jul 05, 2005 1:42 am Post subject: |
|
|
Disciple
Joined: 06 May 2004
Posts: 164
|
My CLASSPATH is set to:
C:\Program Files\IBM\WebSphere MQ\Java\lib\providerutil.jar;C:\Program Files\IBM\WebSphere MQ\Java\lib\com.ibm.mqjms.jar;C:\Program Files\IBM\WebSphere MQ\Java\lib\ldap.jar;C:\Program Files\IBM\WebSphere MQ\Java\lib\jta.jar;C:\Program Files\IBM\WebSphere MQ\Java\lib\jndi.jar;C:\Program Files\IBM\WebSphere MQ\Java\lib\jms.jar;C:\Program Files\IBM\WebSphere MQ\Java\lib\connector.jar;C:\Program Files\IBM\WebSphere MQ\Java\lib\fscontext.jar;C:\Program Files\IBM\WebSphere MQ\Java\lib\com.ibm.mq.jar;.;C:\Program Files\IBM\WebSphere MQ internet pass-thru\lib\MQipt.jar;C:\Program Files\IBM\WebSphere MQ internet pass-thru\lib\guiadmin.jar;C:\Program Files\SQLLIB\java\db2java.zip;C:\Program Files\SQLLIB\java\db2jcc.jar;C:\Program Files\SQLLIB\java\sqlj.zip;C:\Program Files\SQLLIB\bin;C:\Program Files\SQLLIB\java\common.jar;C:\Program Files\SQLLIB\java\db2jcc_license_cisuz.jar;C:\Program Files\SQLLIB\java\db2jcc_license_cu.jar
Everything looks ok in that as far as I'm aware of. (??) |
|
| Back to top |
|
|
| mqmatt |
| Posted: Tue Jul 05, 2005 9:20 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
Your CLASSPATH looks fine.
As fjb_saper said, check your PATH variable - are the MQ commands on it, and does the Config Manager service ID have the authority to run them?
-Matt |
|
| Back to top |
|
|
| bdrummond |
| Posted: Fri Jul 08, 2005 12:25 am Post subject: |
|
|
Disciple
Joined: 06 May 2004
Posts: 164
|
This error has now been solved. I am running the toolkit on a windows 2000 machine which is connected to our network. This is where the problem lies. When attempting to add the Broker to the Toolkit when logged on locally to the machine, no errors are reported.
Still a bit confusing but the Broker is now created within the toolkit and a deploy has been successful. |
|
| Back to top |
|
|
|
|
