| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Transaction using MQPUB/SUB nodes |
« View previous topic :: View next topic » |
| Author |
Message
|
| amigupta1978 |
 Posted: Mon Feb 04, 2002 4:37 pm Post subject: |
 |
|
Centurion
Joined: 22 Jan 2002
Posts: 132
Location: India
|
Hi,
I am using MQSI v2.0.2 on AIX 4.3.3. Can I do transaction using the MQPublish node. For eg say I have the flow MQInput->Compute->MqPublish node which is publishing the message the topic "Error/MQSI". Now I have one subscriber (Qname say TESTQ) to this topic (I mean to Topic Error/#). Can I make my flow in co-ordinated transaction such that if the message doesnot propogate to TESTQ (might be due to some reason say the Q was full or put inhibited) then the message should back out to the input queue. Is this thing possible?? If yes then how can we achieve this?
thanks in Advance
Amit |
|
| Back to top |
|
 |
| mpuetz |
| Posted: Tue Feb 05, 2002 9:15 am Post subject: |
|
|
Centurion
Joined: 05 Jul 2001
Posts: 149
Location: IBM/Central WebSphere Services
|
Hi,
no, this is not possible. For the publishing flow
the TX ends with the put to the publisher entry point
of the broker (which is essentially the BROKER database).
I am currently not quite sure what happens, if forwarding
a fire-and-forget publication to a subscriber fails.
I would expect the broker to retry if the message is persistent
until the forwarding is successful and to drop the message,
if it is non-persistent. But that is a guess (a hole in the
documentation unfortunately).
_________________
Mathias Puetz
IBM/Central WebSphere Services
WebSphere Business Integration Specialist |
|
| Back to top |
|
|
| amigupta1978 |
| Posted: Tue Feb 05, 2002 3:34 pm Post subject: |
|
|
Centurion
Joined: 22 Jan 2002
Posts: 132
Location: India
|
Hi,
Thnx for the reply.
But unfortunately MQSI doesnot retry to put the message, The publisher doesnot care whether the subscriber queue is up or not. The message doesnot propagte to subscriber Q even if the message is persistant when the subscriber queue is pu inhibited (as I have done in my case) So even when I re-change the properties of the subscriber Q to put allowed the previous message is lost.
So I have no other option now but to hardcode the Subscriber queues using the Destination List structure rather than using the PUB-SUB..as I cannot afford to loose any messsage.
Regards,
Amit
|
|
| Back to top |
|
|
| Miriam Kaestner |
| Posted: Wed Feb 13, 2002 4:25 am Post subject: |
|
|
Centurion
Joined: 26 Jun 2001
Posts: 103
Location: IBM IT Education Services, Germany
|
| Publication node always tries to deliver its publication. If the subscriber queue (or, in the case of a remote subscriber queue, the transmission queue) is not reachable, the broker will try to put the message to the DLQ. If this is not possible and the publication flow is transactional, this will cause ALL publications to be rolled back, and normal error processing occurs. |
|
| Back to top |
|
|
| Miriam Kaestner |
| Posted: Wed Feb 13, 2002 4:25 am Post subject: |
|
|
Centurion
Joined: 26 Jun 2001
Posts: 103
Location: IBM IT Education Services, Germany
|
| Publication node always tries to deliver its publication. If the subscriber queue (or, in the case of a remote subscriber queue, the transmission queue) is not reachable, the broker will try to put the message to the DLQ. If this is not possible and the publication flow is transactional, this will cause ALL publications to be rolled back, and normal error processing occurs. |
|
| 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
|
|
|
|
