Hi,
I tried it and it did not work. I even deleted it on the first server, failed
it over and deleted the broker on the second srver and tried to start it. No
luck, same error message.
Just to clarify a few points:
- when I said clustering, I meant hardware clustering and not MQ clustering
- when I said broker, I did not mean MQSI stuff. CSD08 now includes the old
SupportPac MA0C - hence I meant that broker.
There are 6 queue managers on box #1 setup as a hardware cluster. During a
failover Veritas unmounts and then mounts the following disk partitions
between
box #1 and box #2
/var/mqm/data
/var/mqm/log
/var/mqm/errors
Yes, there are 6 queue managers on box #1 but during a failover, the 6 QMs are
stopped (including the brokers) then the EMC disks are mount on the other
server (box #2) then everything is started.
Therefore, it IS the same queue managers / brokers that are being stopped and
started.
Regards,
Roger Lacroix
Capitalware Inc.
http://www.capitalware.biz
Quoting Roger Lacroix <[EMAIL PROTECTED]>:
Hi,
>> try to delete the broker
I'll try it in the morning but these were newly created queue managers.
>> Are the two QMgrs defined in different service groups?
No.
Regards,
Roger Lacroix
Capitalware Inc.
At 12:57 AM 7/20/2005, you wrote:
Roger,
try to delete the broker, switch to the passive node and start it again.
What happens?
If the Broker starts, then switch to the active server. What happens?
Are the two QMgrs defined in different service groups?
Regards
Hubert
> -----Ursprüngliche Nachricht-----
> Von: MQSeries List [SMTP:[EMAIL PROTECTED] im Auftrag
> von Roger Lacroix
> Gesendet am: Mittwoch, 20. Juli 2005 03:48
> An: [email protected]
> Betreff: MQ Pub/Sub problem
>
> All,
>
> At a client site they are starting to use MQ Pub/Sub.
>
> Environment:
> - Solaris 8
> - WMQ v5.3 CSD08 (note: CSD08 includes Pub/Sub libraries for those
> who don't know)
>
> I setup 2 queue managers for 2 applications on a DEV server (single
> server). Everything was going alone fine (except for the usual app
> dev problems), so we decided to test it on the LAB MQ server. The
> LAB MQ server is setup with Veritas with 2 Solaris servers in an
> Active / Passive design.
>
> So, I created the queue managers on the LAB server with hacrtmqm,
> setup the pub/sub queues and then configured the failover support in
> Veritas just like I have done many, many times before. The only new
> item added was an entry under applications for each broker. I enable
> the queue managers and started them and everything was fine.
>
> The application connected and did some testing. Next I failed
> everything over to the passive box. Everything started including the
> new queue managers except for the brokers. After a minute, Veritas
> reports that the 2 brokers have faulted.
>
> I can connect to all queue managers including the new ones and
> get/put messages. From the shell, I typed 'dspmqbrk -m QMgrName' and
> it said it is not active. So, I figured I would manually start the
> broker. When I try to start the broker it said 'not active'. I
> swear, I'm not kidding. So, I typed it really slowing a second time
> and it again said 'not active'. (What I said next, I will not repeat
> here.)
>
> Here are the commands & output from the shell:
>
> [EMAIL PROTECTED]:/export/home/mqm> dspmqbrk -m QMGRNAME
> WebSphere MQ Publish/Subscribe broker for queue manager QMGRNAME not
> active.
>
> [EMAIL PROTECTED]:/export/home/mqm> strmqbrk -m QMGRNAME
> WebSphere MQ Publish/Subscribe broker for queue manager QMGRNAME not
> active.
>
>
> Now for the kicker, I cleared the 2 faults in Veritas and failed it
> back to the first server and EVERYTHING started including the 2
> brokers!!!! So, I failed it again to the second server and
> everything started, queue mangers, listeners, commands servers for
> each queue manager, but the 2 broker would not start!!! I cleared
> the 2 faults in Veritas and failed it back to the first server and
> EVERYTHING started including the 2 brokers!!
>
> What in the world is up? The 2 servers are exactly the same, same
> OS, same kernel patch level and same WMQ 5.3 with the same CSD08.
>
> Anybody got ANY ideas what is going on?
>
> Regards,
> Roger Lacroix
> Capitalware Inc.
>
> Instructions for managing your mailing list subscription are provided in
> the Listserv General Users Guide available at http://www.lsoft.com
> Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html
