| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| AMQ4128 error on starting pub/sub broker |
« View previous topic :: View next topic » |
| Author |
Message
|
| tleichen |
 Posted: Mon Apr 09, 2007 8:05 am Post subject: AMQ4128 error on starting pub/sub broker |
 |
|
Yatiri
Joined: 11 Apr 2005
Posts: 663
Location: Center of the USA
|
We currently start the pub/sub broker with a Java program to start and monitor the broker by doing the commands strmqbrk, dspmqbrk, and endmqbrk. This works fine, but we would like to use a more conventional methodology, as we have learned there are (supposedly) other ways to start the broker.
We are running Websphere MQ v 5.3 CSD 13 on Windows 2000 Server. We are trying to start the pub/sub broker in an automated fashion, as detailed by the online help in the MQ Explorer. When we follow these procedures to the letter, we get an AMQ4128 error in attempting to start the broker with the MQ Explorer.
When we try to start it as a process, the error is as follows:
The service could not be started. The process has ended with return code 0. (AMQ4128)
When we try to start it as a command, the error is shown as:
The service could not be started. Websphere MQ Publish/Subscribe broker started for queue manager qmgr1. (AMQ4128)
In both cases, the broker does not start. Is the help file wrong, or are we missing something?
I'm wondering if we have the start and end commands right for the broker or are there modifications to the .ini file that are required to do things this way? 
_________________
IBM Certified MQSeries Specialist
IBM Certified MQSeries Developer |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Mon Apr 09, 2007 6:46 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
This could be an environment problem. You may have to ultimately set up a script that sets the correct environment variables and then starts/stops the broker...
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| tleichen |
| Posted: Fri Apr 20, 2007 7:19 am Post subject: |
|
|
Yatiri
Joined: 11 Apr 2005
Posts: 663
Location: Center of the USA
|
I just thought I'd post what the problem (and solution) was here. In using an example from the IBM help file, we inadvertently created a parent-child relationship that should not have been there. Furthermore, the broker on the queue manager in question had been established as a child of itself! It would seem to me that this would have no basis and would be something that the vendor should have guarded against. 
Anyway, after using the command, clrmqbrk -m qmgr1 -c qmgr1 to get rid of the parent-child relationship, all was back to normal. 
_________________
IBM Certified MQSeries Specialist
IBM Certified MQSeries Developer |
|
| 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
|
|
|
|
