IBM MQ issue with getting message only on heartbeat interval

Asked Feb 21 '22 at 15:30

Active Feb 22 '22 at 13:42

Viewed 180 times

I have a .net core Worker process using the latest library IBMMQDotnetClient 9.2.4. I am running into a test when there is a about 10k+ messages in queue. the application processes about 5.5k and then it processes random number of messages(mostly one message every heartbeat interval but have seen 100+) for every heartbeat interval time(currently have default value of 5). Has anyone ran into the issue. it would be great if someone knows the cause.

Update: There is no issue when putting message in the Queue it is only when getting from the queue.

edited Feb 22 '22 at 13:42

asked Feb 21 '22 at 15:30

panaroma

Maybe the same problem as described in [this thread](https://stackoverflow.com/a/70701927/638413)? – Daniel Steinmann Feb 21 '22 at 15:43
Is this XMS or just the normal .net API? – JoshMc Feb 21 '22 at 16:49
@DanielSteinmann it does not throw any error it is waiting for the message to come even though the messages are in the queue. – panaroma Feb 22 '22 at 13:39
@JoshMc it is not XMS. – panaroma Feb 22 '22 at 13:40
Are the messages larger than 15k ? – JoshMc Feb 22 '22 at 19:15
the max size for the messages so far is 11kb . – panaroma Feb 22 '22 at 19:27
I would suggest trying at 9.2.0.4 and later when it comes out 9.2.5. If you have a IBM suport contract then open a case with them. – JoshMc Feb 23 '22 at 01:26

IBM MQ issue with getting message only on heartbeat interval

0 Answers0