| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Input handle goes inactive on MQ when MF is idle for long |
« View previous topic :: View next topic » |
| Author |
Message
|
| chaita30 |
 Posted: Sun Dec 05, 2021 9:23 pm Post subject: Input handle goes inactive on MQ when MF is idle for long |
 |
|
Newbie
Joined: 03 Jun 2014
Posts: 7
|
Hi,
I am using IIB10 10.0.0.20 and MQ version 8.0.0.16
A message flow that reads a message from MQ and respond back in an MQ.
Message Flow works fine but struggles to pick messages from MQ when left idle for several hours. I checked MQ handles which shows inactive even when there are messages pilled-up, this gets resolved if I wait for sometime (probably some polling interval but more than 60-120 seconds) or restart integration server. So whenever message flow is idle first batch is delayed, once listers are up again, message flow functions fine until it stay idle for several hours.
Expectation is that it should be always listening and whenever there is a message on a queue even after hours, it should be picked immediately.
I changed following parameter to -1 but has no effect.
| Code: |
| mqsichangeproperties integrationNodeName -e integrationServerName -o Connectors -n sharedConnectorIdleTimeout -v new_timeout_value |
Referred : https://www.ibm.com/docs/en/integration-bus/10.0?topic=flows-websphere-mq-connections
Can someone please help, how this delay can be avoided ? Let me know if any other information is required.
Thanks![/code] |
|
| Back to top |
|
 |
| abhi_thri |
| Posted: Sun Dec 05, 2021 11:17 pm Post subject: |
|
|
Knight
Joined: 17 Jul 2017
Posts: 516
Location: UK
|
hi....what MQ topology are you using, is it client mode or server one? also is the flow using MQInput node or MQGet? Also what exactly is flow doing after consuming a message, is it using any external resources (eg:- database)?
Also, when the messages are stuck what is the value for 'Uncomitted' param at queue status, is it Yes or No? |
|
| Back to top |
|
|
| chaita30 |
| Posted: Tue Dec 07, 2021 11:43 pm Post subject: |
|
|
Newbie
Joined: 03 Jun 2014
Posts: 7
|
Hi,
1. We are using a local queue manager associated with an integration node.
2. Flow is using MQInput Node.
3. Flow calls HTTP service and then puts response back in another queue.
4. Uncommitted Param has zero messages |
|
| Back to top |
|
|
| abhi_thri |
| Posted: Wed Dec 08, 2021 2:45 am Post subject: |
|
|
Knight
Joined: 17 Jul 2017
Posts: 516
Location: UK
|
hi...are you able to recreate this issue for other flows (eg:- a simple MQInput to MQOutput one), if so i guess something is wrong at the fixpack level, time for a PMR as ideally MQInput flows should pick up a message as soon as the flow finished the current UnitOfWork.
Also, if you fancy, prior to raising the PMR you could enable service trace and see whether you can see anything useful in there which explains the delay |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Wed Dec 08, 2021 3:58 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
If you are using MQ Client, and there are no heartbeat packets, the network may be doing an idle timeout, dropping out the MQ connection.
_________________
Glenn |
|
| 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
|
|
|
|
