|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Getting started with the broker - default config error |
« View previous topic :: View next topic » |
Author |
Message
|
elwis |
Posted: Tue Sep 09, 2008 8:11 am Post subject: Getting started with the broker - default config error |
|
|
Apprentice
Joined: 02 Apr 2008 Posts: 26 Location: Sweden
|
Hello all!
I just spent a week playing around with MQ and now it was time to start with the broker. It turns out to be a lot harder, can't even get the default config to run through.
Quote: |
Task: Creating a listener for queue manager [WBRK6_DEFAULT_QUEUE_MANAGER] on port 2414. failed |
And when checking the log it simply says
Quote: |
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
|
I've tried two different physical machines but only reach this point? Is this perhaps a common rookie error
Regards |
|
Back to top |
|
 |
sridhsri |
Posted: Tue Sep 09, 2008 6:22 pm Post subject: |
|
|
Master
Joined: 19 Jun 2008 Posts: 297
|
It appears there is a process running on port 2414. If possible shutdown the process that uses that port. I'm not sure if it is possible to change the settings of the default configuration. The best way out of this is to create the components by hand. It fairly easy to create all the components. |
|
Back to top |
|
 |
elwis |
Posted: Tue Sep 09, 2008 8:37 pm Post subject: |
|
|
Apprentice
Joined: 02 Apr 2008 Posts: 26 Location: Sweden
|
Thanks for answering.
I checked with netstat -ano but no such process seem to be blocking the port. However, I found a walkthrough and created the components manually as you suggested. |
|
Back to top |
|
 |
bower5932 |
Posted: Wed Sep 10, 2008 4:02 am Post subject: |
|
|
 Jedi Knight
Joined: 27 Aug 2001 Posts: 3023 Location: Dallas, TX, USA
|
I've seen this error before, and I didn't have anything running. I rolled back the creation and retried. I got past it the second time. |
|
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
|
|
|
|