MQSeries.net :: View topic

tleichen · Posted: Wed May 02, 2007 8:32 am Post subject:

I've found some more problems with the MQ Explorer on version 5.3 CSD 13 with regard to defining custom services. To illustrate this, I have created four queue managers named TESTA, TESTB, TESTC, and TESTD. I have defined a custom service on TESTA and TESTB to start and stop the pubsub broker on these queue managers. These services are named PubSubA and PubSubB, respectively. This works fine.

When I was doing the same thing for TESTC, I inadvertently typed the parameters that were to be used on TESTD. I did not hit the OK or APPLY buttons, but I did hit the Genereal tab, which caused my definition to be applied, and a PubSubD custom service was defined under TESTC. I then deleted this service (or so I thought), and subsequently entered the desired parameters for PubSubC. I currently have no custom service definitions under queue manager TESTD. When I start TESTC, I get a windows pop-up error that says

X Unable to start /PubSubD Websphere MQ service, return code 40

The Websphere MQ Service was unable to start /PubSubD. The error message
reported was as follows: AMQ8146: Websphere MQ queue manager not available.

Use Websphere MQ Services to determine why the service could not be started.

It gives a similar error when the queue manager is shut down regarding stopping the service. The reason, of course, is obvious! It never should have attempted this because this service was supposedly deleted! It does not appear as a clustom service in the list for either TESTC or TESTD. I even checked the windows registry entries, and I don't see PubSubD in the list of custom services under MQSeries.

In addition, when TESTD is then started, the unwanted service then runs, as the broker is running on it, according to dspmqbrk.

So, my question is... Where the #%$& is this thing coming from and how do I get rid of it?

_________________
IBM Certified MQSeries Specialist
IBM Certified MQSeries Developer