| Author |
Message
|
| mcheong |
 Posted: Sun Jan 21, 2007 9:49 pm Post subject: Error creating Default Configuration in WMB |
 |
|
Newbie
Joined: 21 Jan 2007
Posts: 2
|
Hi I have a problem creating the default configuration in Message Broker Toolkit. It seems like it errors out when trying to create a listener for the queue manager. I am using a windows non domain account (domain account was used to install) to try create this since the domain account is not supported. Both windows accounts have administrative priviledges.
I have updated WMB to 6.02 and there are no longer any software updates available through the Rational Product Updater.
Will really appreciate it if you could lend a hand!
The following are the logs generated in the DefaultConfigurationWizard.log file under {Workspace}/.metadata
| Code: |
+++++++++++++++++++++++++++++++++++ task trace +++++++++++++++++++++++++++++++++++++++++++++
TIMESTAMP [Sat Jan 20 12:16:53 CST 2007]
Checking for the Default Configuration
The above task succeeded
Collected output from task >
Stdout: [MQSI 6.0.0.1
C:\IBM\WMB\6.0
BIP8071I: Successful command completion.]
Stderr: []
+++++++++++++++++++++++++++++++++++ task trace +++++++++++++++++++++++++++++++++++++++++++++
TIMESTAMP [Sat Jan 20 12:16:54 CST 2007]
Checking for the Default Configuration
The above task succeeded
Collected output from task >
Stdout: [MQSI 6.0.0.1
C:\IBM\WMB\6.0
BIP8071I: Successful command completion.]
Stderr: []
+++++++++++++++++++++++++++++++++++ task trace +++++++++++++++++++++++++++++++++++++++++++++
TIMESTAMP [Sat Jan 20 12:20:41 CST 2007]
Checking for the Default Configuration
The above task succeeded
Collected output from task >
Stdout: [MQSI 6.0.0.1
C:\IBM\WMB\6.0
BIP8071I: Successful command completion.]
Stderr: []
+++++++++++++++++++++++++++++++++++ task trace +++++++++++++++++++++++++++++++++++++++++++++
TIMESTAMP [Sat Jan 20 12:20:42 CST 2007]
Checking for the Default Configuration
The above task succeeded
Collected output from task >
Stdout: [MQSI 6.0.0.1
C:\IBM\WMB\6.0
BIP8071I: Successful command completion.]
Stderr: []
+++++++++++++++++++++++++++++++++++ task trace +++++++++++++++++++++++++++++++++++++++++++++
TIMESTAMP [Sat Jan 20 12:20:56 CST 2007]
Verifying that the default queue manager [WBRK6_DEFAULT_QUEUE_MANAGER] does not already exist.
The above task succeeded
Collected output from task >
Stdout: []
Stderr: []
+++++++++++++++++++++++++++++++++++ task trace +++++++++++++++++++++++++++++++++++++++++++++
TIMESTAMP [Sat Jan 20 12:20:57 CST 2007]
Verifying that the default broker [WBRK6_DEFAULT_BROKER] does not already exist.
The above task succeeded
Collected output from task >
Stdout: [MQSI 6.0.0.1
C:\IBM\WMB\6.0
BIP8013E: Component does not exist.
A component may only be used if it has first been created.
No user action required.]
Stderr: []
+++++++++++++++++++++++++++++++++++ task trace +++++++++++++++++++++++++++++++++++++++++++++
TIMESTAMP [Sat Jan 20 12:21:06 CST 2007]
Verifying that the default broker database [DEFBKDB6] does not already exist.
The above task succeeded
Collected output from task >
Stdout: [C:\IBM\WMBToolkit\6.0\evtoolkit\eclipse\plugins\com.ibm.etools.mft.eou.win32_6.0.0.2>db2 start database manager
DB20000I The START DATABASE MANAGER command completed successfully.
C:\IBM\WMBToolkit\6.0\evtoolkit\eclipse\plugins\com.ibm.etools.mft.eou.win32_6.0.0.2>echo off
C:\IBM\WMBToolkit\6.0\evtoolkit\eclipse\plugins\com.ibm.etools.mft.eou.win32_6.0.0.2>db2 terminate
DB20000I The TERMINATE command completed successfully.
C:\IBM\WMBToolkit\6.0\evtoolkit\eclipse\plugins\com.ibm.etools.mft.eou.win32_6.0.0.2>echo off
C:\IBM\WMBToolkit\6.0\evtoolkit\eclipse\plugins\com.ibm.etools.mft.eou.win32_6.0.0.2>db2 list database directory
SQL1031N The database directory cannot be found on the indicated file system.
SQLSTATE=58031
C:\IBM\WMBToolkit\6.0\evtoolkit\eclipse\plugins\com.ibm.etools.mft.eou.win32_6.0.0.2>echo off]
Stderr: []
+++++++++++++++++++++++++++++++++++ task trace +++++++++++++++++++++++++++++++++++++++++++++
TIMESTAMP [Sat Jan 20 12:21:07 CST 2007]
Verifying that the default Configuration Manager [WBRK6_DEFAULT_CONFIGURATION_MANAGER] does not already exist.
The above task succeeded
Collected output from task >
Stdout: [MQSI 6.0.0.1
C:\IBM\WMB\6.0
BIP8013E: Component does not exist.
A component may only be used if it has first been created.
No user action required.]
Stderr: []
+++++++++++++++++++++++++++++++++++ task trace +++++++++++++++++++++++++++++++++++++++++++++
TIMESTAMP [Sat Jan 20 12:21:08 CST 2007]
Verifying that the local domain connection file does not already exist.
The above task succeeded
Collected output from task >
Stdout: []
Stderr: []
+++++++++++++++++++++++++++++++++++ task trace +++++++++++++++++++++++++++++++++++++++++++++
TIMESTAMP [Sat Jan 20 12:21:24 CST 2007]
Creating the database [DEFBKDB6] for the default broker.
The above task succeeded
Collected output from task >
Stdout: [MQSI 6.0.0.1
C:\IBM\WMB\6.0
C:\IBM\WMBToolkit\6.0>CALL mqsicreatedb DEFBKDB6 -i Kevin -a *********
BIP9824I: Creating the DatabaseInstanceMgr Service Component.
BIP9832I: Starting the DatabaseInstanceMgr Service Component.
BIP9828I: Connecting to the Cloudscape Network Server on port 1527.
BIP9809I: Creating Derby Database 'DEFBKDB6', this may take a while.
BIP9829I: Cataloging the Derby Database 'DEFBKDB6'.
BIP9818I: IBM Cloudscape/Apache Derby was used to create the 'DEFBKDB6' database.
BIP8071I: Successful command completion.
C:\IBM\WMBToolkit\6.0>exit]
Stderr: []
+++++++++++++++++++++++++++++++++++ task trace +++++++++++++++++++++++++++++++++++++++++++++
TIMESTAMP [Sat Jan 20 12:21:48 CST 2007]
Creating the Configuration Manager. [WBRK6_DEFAULT_CONFIGURATION_MANAGER]
The above task succeeded
Collected output from task >
Stdout: [MQSI 6.0.0.1
C:\IBM\WMB\6.0
C:\IBM\WMBToolkit\6.0>mqsicreateconfigmgr -i Kevin -a ********* -q WBRK6_DEFAULT_QUEUE_MANAGER WBRK6_DEFAULT_CONFIGURATION_MANAGER
BIP8071I: Successful command completion.
C:\IBM\WMBToolkit\6.0>exit]
Stderr: [WebSphere MQ queue manager created.
Creating or replacing default objects for WBRK6_DEFAULT_QUEUE_MANAGER.
Default objects statistics : 43 created. 0 replaced. 0 failed.
Completing setup.
Setup completed.
WebSphere MQ queue manager 'WBRK6_DEFAULT_QUEUE_MANAGER' starting.
5 log records accessed on queue manager 'WBRK6_DEFAULT_QUEUE_MANAGER' during the log replay phase.
Log replay for queue manager 'WBRK6_DEFAULT_QUEUE_MANAGER' complete.
Transaction manager state recovered for queue manager 'WBRK6_DEFAULT_QUEUE_MANAGER'.
WebSphere MQ queue manager 'WBRK6_DEFAULT_QUEUE_MANAGER' started.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.]
+++++++++++++++++++++++++++++++++++ task trace +++++++++++++++++++++++++++++++++++++++++++++
TIMESTAMP [Sat Jan 20 12:21:58 CST 2007]
Creating the default broker. [WBRK6_DEFAULT_BROKER]
The above task succeeded
Collected output from task >
Stdout: [MQSI 6.0.0.1
C:\IBM\WMB\6.0
C:\IBM\WMBToolkit\6.0>mqsicreatebroker WBRK6_DEFAULT_BROKER -i Kevin -a ********* -q WBRK6_DEFAULT_QUEUE_MANAGER -n DEFBKDB6
BIP8071I: Successful command completion.
C:\IBM\WMBToolkit\6.0>exit]
Stderr: [AMQ8110: WebSphere MQ queue manager already exists.
WebSphere MQ queue manager running.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.]
+++++++++++++++++++++++++++++++++++ task trace +++++++++++++++++++++++++++++++++++++++++++++
TIMESTAMP [Sat Jan 20 12:21:59 CST 2007]
Creating a listener for queue manager [WBRK6_DEFAULT_QUEUE_MANAGER] on port 2414.
Status ERROR: com.ibm.etools.mft.eou code=0 Could not create the listener.
Collected output from task >
Stdout: [5724-H72 (C) Copyright IBM Corp. 1994, 2004. ALL RIGHTS RESERVED.
Listener creation no longer supported
Active Connections
|
|
|
| Back to top |
|
 |
| pathipati |
| Posted: Mon Jan 22, 2007 5:27 am Post subject: |
|
|
Master
Joined: 03 Mar 2006
Posts: 296
|
| try manually creating listener for queue manager. |
|
| Back to top |
|
|
| rodmill |
| Posted: Thu Feb 01, 2007 7:53 pm Post subject: MB default config wizard Listener creation no longer support |
|
|
Novice
Joined: 01 Feb 2007
Posts: 13
|
I have this problem too, and it is preventing me from implementing
Toolkit 602. The default configuration wizard will not let me define
the listener. I would report it to IBM support if I could, but I do not have
a customer number!
We use the wizard in MB training courses.
Does anyone have a workaround? |
|
| Back to top |
|
|
| pathipati |
| Posted: Thu Feb 01, 2007 7:56 pm Post subject: |
|
|
Master
Joined: 03 Mar 2006
Posts: 296
|
| Quote: |
| I have this problem too, and it is preventing me from implementing Toolkit 602 |
What problem do you've exactly? |
|
| Back to top |
|
|
| rodmill |
| Posted: Thu Feb 01, 2007 8:18 pm Post subject: |
|
|
Novice
Joined: 01 Feb 2007
Posts: 13
|
Same problem as reported by mcheong, but here it is in my words:
The default configuration wizard works reliably until applying Toolkit 602,
then, when it creates the listener it fails with the error:
"Listener creation no longer supported".
It only gives you 2 options: rollback, or fix the error and continue.
Fixing the error seems to require that the wizard will be able to create the
listener and continue, but it cannot do that, so it is stuck. Then you just have
to click the rollback button.
Here is a fragment from:
C:\Documents and Settings\mq05\IBM\wmbt6.0\workspace\.metadata\DefaultConfigurationWizard.log
+++++++++++++++++++++++++++++++++++ task trace +++++++++++++++++++++++++++++++++++++++++++++
TIMESTAMP [Fri Feb 02 14:17:37 EST 2007]
Creating a listener for queue manager [WBRK6_DEFAULT_QUEUE_MANAGER] on port 2414.
Status ERROR: com.ibm.etools.mft.eou code=0 Could not create the listener.
Collected output from task >
Stdout: [5724-H72 (C) Copyright IBM Corp. 1994, 2004. ALL RIGHTS RESERVED.
Listener creation no longer supported |
|
| Back to top |
|
|
| pathipati |
| Posted: Fri Feb 02, 2007 5:29 am Post subject: |
|
|
Master
Joined: 03 Mar 2006
Posts: 296
|
| What is your MQ version and Broker runtime version? |
|
| Back to top |
|
|
| mcheong |
| Posted: Fri Feb 02, 2007 7:18 am Post subject: |
|
|
Newbie
Joined: 21 Jan 2007
Posts: 2
|
I actually got my problem fixed. Sorry for not replying. For some reason the installation conflicted with my installation of RAD. Uninstalling RAD was the only option that I had. Now this is strange because my colleague escaped this problem. All he had to do was reinstall WMB. And WMB is better installed directly under C drive instead of being under the Program Files directory. This is to do with the limit of characters that Windows allows.
If you're still having problems creating the listener, try doing that manually when the error pops up. Open up MQ Explorer and create the listener under the Default Queue Manager that was created for you.
Also disable the Windows firewall before running the Default Configuration. Hope this helps. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Feb 02, 2007 7:22 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
WMB Toolkit v6 and RAD always share the same eclipse shell. Even if you tell them to install in different directories, you will only ever end up with one eclipse executable.
It is always better to install any Eclipse or java based application in a directory that has no spaces in the full path.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| rodmill |
| Posted: Fri Feb 02, 2007 1:29 pm Post subject: |
|
|
Novice
Joined: 01 Feb 2007
Posts: 13
|
Thanks for you comments. It is sounding like I have installed something incorrectly and other problems are likely to come up later, so I would like to fix the underlying problem, rather than bypass this problem.
The system is a master image use for cloning (by Symantec Ghost) so it has had very little use, defined history, but lots of testing (the clones work well and are extensively used).
======Here is its complete history (only 4 days)===============
16/4/2006: Windows XP on NTFS
Eclipse 3.0.1
WMQ v6, Fix Pack 1 (no domain controllers)
(Java from Fix Pack not done)
MS Visual Studio .NET 2003 (Visual C++, Visual Basic)
17/5/2006
Added WebSphere Message Broker v6 from downloaded software from the XL web site
C85RAML WMB v6 >>>> Broker 6.0.0.0
C88HHML Documentation
C88HIML CD 1
C88HJML CD 2
C88HKML CD 3
C88HLML CD 4
C88HMML CD 5 >>>> Toolkit 6.0.0.1 ("Add Feat - NO")
C88KYML RAC >>>> RAC 6.0.1
Tested the default configuration
db2nodes.cfg updated to say "localhost LOCALHOST" rather than the system name
DB2 should now be name independent (a red sub-icon has appeared on the DB2 green icon)
SET MQNOREMPOOL=1 (in Control Panel-System-System-System Properties)
2/11/2006
Rational Product Update 6.0.1 essential & was already present
MB60_6002 Fix Pack 1+2 installed using RPU (Install Updates)
((mqsiservice -v still shows 6.000, not 6002 as would be expected))
Installed IS02 Message Broker Admin Plugin into MQ Explorer
Userid left as MQSIUSER/MQSIPASS
23/1/2007
MQ RefreshPack 2 (6.0.2.0)
(Deleted P-F-\IBM\WMQ-\Maint_1.0 & Maint_2.0)
WMB (MQSI) FixPack 3 (6003)
Debug/change variable problem fixed
WMB (MQSI) Toolkit 602 available but not installed yet as fails with "listener not supported"
Following MQ supportpacs installed/updated:
IH03 RFHUTIL
MA01 q program
MO03 qload program
MO71 mqmonntp program for admin
MO72 mqsc program for admin
MS03 saveqmgr
Java (J2SE 5.10) updated from Sun
All Microsoft Windows patches have been kept up-to-date by someone else. |
|
| Back to top |
|
|
| rodmill |
| Posted: Fri Feb 02, 2007 1:33 pm Post subject: |
|
|
Novice
Joined: 01 Feb 2007
Posts: 13
|
Please note that this system does not have RAD (Rational Application Develper) installed. It does have RAC (for the debug component) and RPU for the updating.
Thanks for your help in this matter. |
|
| Back to top |
|
|
| David.Partridge |
| Posted: Tue May 15, 2007 6:39 am Post subject: |
|
|
Master
Joined: 28 Jun 2001
Posts: 249
|
I too just had this problem and have a resolution for you:
Add the ...\WebSphere MQ\bin\amqrmppa.exe
to the Windows Firewall list of authorised programs, and it should then work fine.
Dave |
|
| Back to top |
|
|
| Bill.Matthews |
| Posted: Tue May 15, 2007 6:38 pm Post subject: |
|
|
Master
Joined: 23 Sep 2003
Posts: 232
Location: IBM (Retired)
|
WMB v6.0.2 iFix006 includes a fix for this problem. The default configuration wizard now creates the queue manager listener for port 2414.
_________________
Bill Matthews |
|
| Back to top |
|
|
|
|
