| Author |
Message |
 Topic: Cluster and XA |
gerco
Replies: 14
Views: 9510
|
 Forum: Clustering Posted: Mon Jan 14, 2008 8:26 am Subject: Cluster and XA |
I think you hit the nail on its head. Apparently a very recent bug fix (sometimes you just have to be lucky).
I tried it at my clean test environment, and their it worked fine. We will try to imple ... |
| Topic: Cluster and XA |
gerco
Replies: 14
Views: 9510
|
Forum: Clustering Posted: Fri Jan 11, 2008 12:50 pm Subject: Cluster and XA |
| It didn't make sense to me either. Will try to get IBM involved and let you know once we found the problem. |
| Topic: Cluster and XA |
gerco
Replies: 14
Views: 9510
|
Forum: Clustering Posted: Thu Jan 10, 2008 8:12 am Subject: Cluster and XA |
Trigger Control: on
Trigger Type: first
Trigger Depth: 1
Trigger Message Priority: 0
Trigger Data: -
Initiation Queue Name: -
Process Name: - |
| Topic: Cluster and XA |
gerco
Replies: 14
Views: 9510
|
Forum: Clustering Posted: Thu Jan 10, 2008 6:00 am Subject: Cluster and XA |
>>Is your channel initiator running?
Channel initiator is running.
>>Did someone play around with the properties of SYSTEM.CLUSTER.TRANSMIT.QUEUE?
No, it is a clean install on clean vi ... |
| Topic: Cluster and XA |
gerco
Replies: 14
Views: 9510
|
Forum: Clustering Posted: Thu Jan 10, 2008 5:12 am Subject: Cluster and XA |
Yes, they are visible in the SYSTEM.CLUSTER.TRANSMIT.QUEUE and can be opened.
It seems to me (although I am not an expert) that MQ has accepted the message, has forwarded the message to the QM wher ... |
| Topic: Cluster and XA |
gerco
Replies: 14
Views: 9510
|
Forum: Clustering Posted: Thu Jan 10, 2008 4:51 am Subject: Cluster and XA |
Hmm, don't think that's the case.
First of all, in that case the Tux client would have got a transaction time out.
Secondly, MQ has accepted the message. After all, as soon as the channels are ... |
| Topic: Cluster and XA |
gerco
Replies: 14
Views: 9510
|
Forum: Clustering Posted: Thu Jan 10, 2008 2:21 am Subject: Cluster and XA |
Hello,
I have the following setup, using WMQ 5.3:
- Queue manager QM1 at Server 1
- Queue manager QM2 at Server 2, hosting queue q2 which is shared in the cluster.
- Cluster with QM1 and QM2
... |
