| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Message expiry |
« View previous topic :: View next topic » |
| Author |
Message
|
| Chris-TH |
 Posted: Sun Dec 04, 2011 10:31 pm Post subject: Message expiry |
 |
|
Newbie
Joined: 04 Dec 2011
Posts: 3
|
Hi,
I'm new to MQ/MB so hopefully this is not a stupid question.
I have developed an interface to a subsystem. The subsystem will connect to a TCPIPServer (in/out). There is a requirement for a heartbeat being sent and I implemented it this way:
Timeout notification -> Compute -> TCPIPServerOutput
The interface is working pretty much according to specifications, but I noticed something with the heartbeat:
If there is no client connected to the TCPIP server, the heartbeats are being "queued" internally in the flow. That means heartbeat messages generated every minute are being kept and all sent when a client connects. I noticed that when I connected a client and 8 hours worth of heartbeats were being sent!!!
So my question is: Is there a timer that I can use to make the heartbeats expire?
I know that there is a timer for messages on a queue, but this is not over a queue but directly from the compute node to the Output node. |
|
| Back to top |
|
 |
| paintpot |
| Posted: Mon Dec 05, 2011 9:21 am Post subject: |
|
|
Centurion
Joined: 19 Sep 2005
Posts: 112
Location: UK
|
I would suggest connecting your TCPIPServerOutput node failure terminal - it can then route your failures to a notification system - where you could aggregate them / delete them etc.
Of course, you could even decide not to do anything and just lose them.
I've not tried this, so have fun testing! the principle ought to be ok. |
|
| Back to top |
|
|
| Chris-TH |
| Posted: Mon Dec 05, 2011 9:59 am Post subject: |
|
|
Newbie
Joined: 04 Dec 2011
Posts: 3
|
| Well, that is what I wanted to avoid (keeping track of the status of the connection). In that case I would be better off with a shared variable that holds the status of the TCPIP connection. Then in my compute node I would just propagate the heartbeats to 'nowhere' if the connection is down. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Dec 05, 2011 10:08 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
|
| Back to top |
|
|
| Chris-TH |
| Posted: Tue Dec 06, 2011 12:17 am Post subject: |
|
|
Newbie
Joined: 04 Dec 2011
Posts: 3
|
Thank you for that hint. It look like I need to attach a compute node to the catch terminal and inside that node, propagate to 'nowhere'
I'll try that out. |
|
| 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
|
|
|
|
