| Author |
Message
|
| kpvin |
 Posted: Tue May 27, 2008 1:17 am Post subject: WebSphere Message Broker 6.0 Issues |
 |
|
Novice
Joined: 02 Jan 2004
Posts: 17
|
Hi,
Have installed WMB6.0, WMB Toolkit with pre-requisite softwares (MQ, DB2) on windows. Also, applied fp for mq 6.0.2.3 and wmb 6.0.0.7 respectively.
While creating default configuration for WMB getting msg"Creating local domian connection (LocalDomain.configmgr)failed; Could not connect to the Configuration Manager. Default QMGR, Broker and ConfigMgr were created and running successfully. However, am getting this error and unable to continue with the default configuration.
Attached below metadata log details for the default config wizard:
-------------------------------------------------------------------------------------
+++++++++++++++++++++++++++++++++++ task trace +++++++++++++++++++++++++++++++++++++++++++++
TIMESTAMP [Tue May 27 14:01:59 IST 2008]
Setting the service [IBM MQSeries Broker WBRK6_DEFAULT_CONFIGURATION_MANAGER] to start automatically.
The above task succeeded
Collected output from task >
Stdout: []
Stderr: []
+++++++++++++++++++++++++++++++++++ task trace +++++++++++++++++++++++++++++++++++++++++++++
TIMESTAMP [Tue May 27 14:01:59 IST 2008]
Setting the service [IBM MQSeries Broker WBRK6_DEFAULT_BROKER] to start automatically.
The above task succeeded
Collected output from task >
Stdout: []
Stderr: []
+++++++++++++++++++++++++++++++++++ task trace +++++++++++++++++++++++++++++++++++++++++++++
TIMESTAMP [Tue May 27 14:02:00 IST 2008]
Setting the Configuration Manager's Queue Manager automatic startup property.
The above task succeeded
Collected output from task >
Stdout: [5724-H72 (C) Copyright IBM Corp. 1994, 2004. ALL RIGHTS RESERVED.
Queue Manager 'WBRK6_DEFAULT_QUEUE_MANAGER' successfully set to 'Automatic' mode]
Stderr: []
+++++++++++++++++++++++++++++++++++ task trace +++++++++++++++++++++++++++++++++++++++++++++
TIMESTAMP [Tue May 27 14:02:02 IST 2008]
Starting the Configuration Manager [WBRK6_DEFAULT_CONFIGURATION_MANAGER].
The above task succeeded
Collected output from task >
Stdout: [MQSI 6.0.0.7
C:\Program Files\IBM\MQSI\6.0
C:\Program Files\IBM\MessageBrokersToolkit\6.0>mqsistart WBRK6_DEFAULT_CONFIGURATION_MANAGER
BIP8096I: Successful command initiation, check the system log to ensure that the component started without problem and that it continues to run without problem.
C:\Program Files\IBM\MessageBrokersToolkit\6.0>exit]
Stderr: [WebSphere MQ queue manager running.]
+++++++++++++++++++++++++++++++++++ task trace +++++++++++++++++++++++++++++++++++++++++++++
TIMESTAMP [Tue May 27 14:02:03 IST 2008]
Starting the default broker [WBRK6_DEFAULT_BROKER].
The above task succeeded
Collected output from task >
Stdout: [MQSI 6.0.0.7
C:\Program Files\IBM\MQSI\6.0
C:\Program Files\IBM\MessageBrokersToolkit\6.0>mqsistart WBRK6_DEFAULT_BROKER
BIP8096I: Successful command initiation, check the system log to ensure that the component started without problem and that it continues to run without problem.
C:\Program Files\IBM\MessageBrokersToolkit\6.0>exit]
Stderr: [WebSphere MQ queue manager running.]
+++++++++++++++++++++++++++++++++++ task trace +++++++++++++++++++++++++++++++++++++++++++++
TIMESTAMP [Tue May 27 14:03:06 IST 2008]
Creating the local domain connection [LocalDomain.configmgr].
Status ERROR: com.ibm.etools.mft.eou code=0 Could not create the local domain connection [LocalDomain.configmgr].
Collected output from task >
Stdout: []
Stderr: [] java.lang.Exception: Could not connect to the Configuration Manager. Check the event log to see if the Configuration Manager started successfully.
-------------------------------------------------------------------------------------
Any help in this regard is highly appreciated.
Thank you. |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Tue May 27, 2008 1:21 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
run 'eventvwr' and see what it says.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| kpvin |
| Posted: Tue May 27, 2008 1:42 am Post subject: |
|
|
Novice
Joined: 02 Jan 2004
Posts: 17
|
Tried stopping configmgr and started again...i see in apps logs config mge is not avbl for use.
Below is Apps log details:
( WBRK6_DEFAULT_CONFIGURATION_MANAGER ) The Configuration Manager is not available for use.
A problem has been encountered while trying to start the Configuration Manager. The problem is not expected to be transient.
Stop the Configuration Manager using the mqsistop command. Look at previous error messages for the Configuration Manager in the event log. Determine and correct the cause of the problem before attempting to start the Configuration Manager again. If the problem persists contact your IBM support center. |
|
| Back to top |
|
|
| kpvin |
| Posted: Tue May 27, 2008 1:47 am Post subject: |
|
|
Novice
Joined: 02 Jan 2004
Posts: 17
|
| In addition to my first message, also getting er msg: "bipbroker.exe - Unable to Locate Companent : The application has failed to start because MQM.dll was not found. reinstalling the application may fix this problem." |
|
| Back to top |
|
|
| Gaya3 |
| Posted: Tue May 27, 2008 1:50 am Post subject: |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
what jeff asked you to do so is: to check the Event Viewer logs
i suspect you deleted the broker and recreated it right
Regards
Gayathri
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
| kpvin |
| Posted: Tue May 27, 2008 4:41 am Post subject: |
|
|
Novice
Joined: 02 Jan 2004
Posts: 17
|
Hi,
Above log details are from Event Viewer Apps Log.
No i have not touched the broker.
Thank you |
|
| Back to top |
|
|
| prince_mq |
| Posted: Tue May 27, 2008 6:43 am Post subject: |
|
|
Voyager
Joined: 10 Aug 2006
Posts: 76
|
|
| Back to top |
|
|
| patb23 |
| Posted: Mon Jul 07, 2008 5:35 am Post subject: |
|
|
Newbie
Joined: 25 Oct 2006
Posts: 4
|
I am also experiencing the same problem but as Gaya3 mentioned I happ. to reinstall the Broker. How that would cause the problem and what I need to do to fix that.
Thank you |
|
| Back to top |
|
|
| AkankshA |
| Posted: Mon Jul 07, 2008 5:50 am Post subject: |
|
|
Grand Master
Joined: 12 Jan 2006
Posts: 1494
Location: Singapore
|
| patb23 wrote: |
I am also experiencing the same problem but as Gaya3 mentioned I happ. to reinstall the Broker. How that would cause the problem and what I need to do to fix that.
Thank you |
did u reinstall the broker runtime component or recreated broker.. ???
_________________
Cheers |
|
| Back to top |
|
|
| patb23 |
| Posted: Mon Jul 07, 2008 6:11 am Post subject: |
|
|
Newbie
Joined: 25 Oct 2006
Posts: 4
|
I reinstalled the Runtime as I thought it is a PATH issue.
Also, In the MQ Explorer, I see the WBRK61_DEFAULT_QUEUE_MANAGER created and running but am not able to connect to this from MB Toolkit. |
|
| Back to top |
|
|
| AkankshA |
| Posted: Mon Jul 07, 2008 6:16 am Post subject: |
|
|
Grand Master
Joined: 12 Jan 2006
Posts: 1494
Location: Singapore
|
MQ Explorer show you the queue managers
are your channels up ??/
si your listener running ???
_________________
Cheers |
|
| Back to top |
|
|
| patb23 |
| Posted: Mon Jul 07, 2008 6:19 am Post subject: |
|
|
Newbie
Joined: 25 Oct 2006
Posts: 4
|
| Yes. The channel and QM are running. |
|
| Back to top |
|
|
|
|
