| Author |
Message
|
| nmaddisetti |
 Posted: Tue Mar 21, 2006 3:16 am Post subject: Problem with Expiry report |
 |
|
Centurion
Joined: 06 Oct 2004
Posts: 145
|
Hi,
Iam using MQ 6.0. on AIX.
What should i do to get the Expiry report immediatly on expiration.
Right now iam getting Expiry report to the specifed reply to queue after some time interval.(if iam giving 60 second sexpiry time iam getting report after 3 or 4 minits)
but i need expiry report immediatly on expiration.
I looked into many posts here every where they are saying that expired message will be dicarded from the queue only when when we look for message on that queue and expiry report will be generated when it is discarded. In this way only this will happen or is there any other way to refresh the queues for expired messages automatically.
Thanks,
nmaddisetti. |
|
| Back to top |
|
 |
| wschutz |
| Posted: Tue Mar 21, 2006 3:28 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
You will only get the expired message report when
(1) an application tries to do an MQGET, which causes the qmgr to realize the message is expired and generate a report
(2) the queue manager automatically scans the queue looking for expired messages. In V6 on distributed, you do not have control over how frequently this happens (see this post: http://www.mqseries.net/phpBB2/viewtopic.php?t=23720 )
_________________
-wayne |
|
| Back to top |
|
|
| javagate |
| Posted: Tue Mar 21, 2006 3:39 am Post subject: |
|
|
Disciple
Joined: 15 Nov 2004
Posts: 159
|
I believe this is simular to what z/OS currently has.
Manually +SSID REFRESH QMGR TYPE(EXPIRY) NAME(*)
or ALTER QMGR EXPRYINT( ss )
But on z/OS this causes a run on buffers.
_________________
WebSphere Application Server 7.0 z/OS &
MQ 6.0. I work with WebSphere in the real world not in some IBM lab. |
|
| Back to top |
|
|
| nmaddisetti |
| Posted: Tue Mar 21, 2006 3:48 am Post subject: |
|
|
Centurion
Joined: 06 Oct 2004
Posts: 145
|
Hi ,
wschutz,
As u suggested, I cant go for this as expiry time is very less in our case .
javagate,
I think ALTER QMGR EXPRYINT( ss )
is supported on z/Os only.
can you people suggest something else.
Thanks,
nmaddisetti. |
|
| Back to top |
|
|
| wschutz |
| Posted: Tue Mar 21, 2006 4:10 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
You can only change the expiry scan interval on zOS.
There is a supportpac (mo01) that contains a program which will scan one or all queues for expired messages. I haven't used it, but if you need to drive a low expiry detection time, I think that would be your best bet.
_________________
-wayne |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Mar 21, 2006 5:03 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
I would go a little bit further and question his model. Why do you need the expiry report in such a timely fashion?
The absence of any correlated message within the timeout period should be enough to trigger your business process.
The timeout report should then be some asynchronous / write to log thing
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
