ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » IBM MQ Performance Monitoring » message delay

Post new topic  Reply to topic
 message delay « View previous topic :: View next topic » 
Author Message
sharonv
PostPosted: Thu Jan 16, 2014 2:47 am    Post subject: message delay Reply with quote

Apprentice

Joined: 03 Feb 2011
Posts: 27

Hi
I'm using MQ 7.0.1.11
We have a queue which we set up the performance event
the high depth was set to 1 to each time a meesage enters the event is created
we listen to the event queue and catch the event message then we notify our application that a message is in the queue
the application does mqget and then also check for the current queue depth to see if any more messages exists

we noticed the following , a mesage is sent ( small one no loads)
the event is created , the application does the mq get and recieves no messages then check the queue depth and it is 1
it does a loop like that and we find out it takes about half a second until the message appears in the queue
we have several queue manager in which we dont see this delay

any idea anyone ?
Back to top
View user's profile Send private message
exerk
PostPosted: Thu Jan 16, 2014 3:59 am    Post subject: Re: message delay Reply with quote

Jedi Council

Joined: 02 Nov 2006
Posts: 6339

sharonv wrote:
...we listen to the event queue and catch the event message then we notify our application that a message is in the queue the application does mqget and then also check for the current queue depth to see if any more messages exists

Why? Why does the app not do a GET with wait, or why do you not trigger the application?

sharonv wrote:
...we noticed the following , a mesage is sent ( small one no loads) the event is created , the application does the mq get and recieves no messages then check the queue depth and it is 1 it does a loop like that and we find out it takes about half a second until the message appears in the queue we have several queue manager in which we dont see this delay

Probably because the message has not been committed by the putting application.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys.
Back to top
View user's profile Send private message
zpat
PostPosted: Thu Jan 16, 2014 6:05 am    Post subject: Reply with quote

Jedi Council

Joined: 19 May 2001
Posts: 5849
Location: UK

Ex-erk is correct.

A conventional triggered queue approach would be better. Or for high volumes using long running application with a MQGMO_WAIT.
_________________
Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error.
Back to top
View user's profile Send private message
sharonv
PostPosted: Sun Jan 19, 2014 12:16 am    Post subject: Reply with quote

Apprentice

Joined: 03 Feb 2011
Posts: 27

Hi
The application was writen long time ago ,
and it will take time to change it , as it is running in production mode
can you explain why there is half a second delay between the time
we see the current depth increasing and when the message is available
is there anything to do with the current situation

is it possible that the current depth will increase and yet the message will be in the queue yet ?
Back to top
View user's profile Send private message
zpat
PostPosted: Sun Jan 19, 2014 1:07 am    Post subject: Reply with quote

Jedi Council

Joined: 19 May 2001
Posts: 5849
Location: UK

The usual reason for any disparity in queue depth and the messages available on the queue is due to uncommitted messages.
_________________
Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error.
Back to top
View user's profile Send private message
PeterPotkay
PostPosted: Sun Jan 19, 2014 6:33 am    Post subject: Reply with quote

Poobah

Joined: 15 May 2001
Posts: 7716

Trigger messages don't get committed until the app messages that generated them is committed - which avoids apps from getting triggered prematurely.

Apps that sit on a queue and MQGET with wait don't receive the message until the message is committed.

Use Event messages and/or checking queue depth to see if there is a message to get is a bad design.

A half second delay is causing you a problem, or its just a curiosity you would like to understand?
_________________
Peter Potkay
Keep Calm and MQ On
Back to top
View user's profile Send private message
bruce2359
PostPosted: Sun Jan 19, 2014 6:48 am    Post subject: Reply with quote

Poobah

Joined: 05 Jan 2008
Posts: 9399
Location: US: west coast, almost. Otherwise, enroute.

sharonv wrote:
The application was writen long time ago ,
and it will take time to change it , as it is running in production mode

Has it always behaved with this delay? Or, is this delay new behavior? When was the program last compiled?
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » IBM MQ Performance Monitoring » message delay
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.