f A Tressler [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 07, 2004 1:59 PM
To: [EMAIL PROTECTED]
Subject: Re: Clearing Expiry Messages
>Set an Expiry just above your Wait Interval
>is valid, but keep in mind that your queues
>will be cleared almost immediately of any
>orphaned mes
04:04
To: [EMAIL PROTECTED]
Subject: Re: Clearing Expiry Messages
Further to this another excerpt from the SAG.
Expired messages on z/OS
On WebSphere MQ for z/OS, messages that have expired are discarded by the
next appropriate MQGET call. However, if no such call occurs, the expired
message is not dis
: Thursday, 8 April 2004 12:46 PM
To: [EMAIL PROTECTED]
Subject: Re: Clearing Expiry Messages
You're right Gregg, the behaviour I described occurs in MQSeries v2.1 and
earlier. I missed this enhancement when looking at the upgrade to 5.3.
Back on the original question, you still have to browse pas
IL PROTECTED]To: [EMAIL PROTECTED]
COM> cc:
Sent by: MQSeries Subject: Re: Clearing Expiry Messages
List
Title: Clearing expiry messages
The following is the extracts from System Administration manual (V5.3):
"In the current implementations, the message is discarded when a browse or nonbrowse MQGET call occurs that would have returned the message had it not already expired&q
: Wednesday, April 07, 2004 6:26 PM
To: [EMAIL PROTECTED]
Subject: Re: Clearing Expiry Messages
Hi guys,
my experience with GET via correlid (both MF and distributed) indicates
that a GET via correlid at current WMQ levels does not clean the queue. On
MF, you need to do a destructive get, which
"Potkay, Peter M
(PLC, IT)" To: [EMAIL PROTECTED]
<[EMAIL PROTECTED]cc:
RTFORD.COM> Subject: Re: Clearing Expiry Messages
S
To: [EMAIL PROTECTED]
<[EMAIL PROTECTED]cc:
RTFORD.COM> Subject: Re: Clearing Expiry Messages
Sent by: MQSeries
List
<[EMAIL PROTECTED]
even
for a specific ID.
-Original Message-
From: Jeff A Tressler [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 07, 2004 4:59 PM
To: [EMAIL PROTECTED]
Subject: Re: Clearing Expiry Messages
>Set an Expiry just above your Wait Interval
>is valid, but keep in mind that your queues
>Set an Expiry just above your Wait Interval
>is valid, but keep in mind that your queues
>will be cleared almost immediately of any
>orphaned messages as subsequent gets execute.
>
This is what I understand in general, here is
the specifics of my issue and how I understand
the issue.
Our applicat
) [mailto:[EMAIL PROTECTED]
Sent: Thursday, 8 April 2004 5:44 AM
To: [EMAIL PROTECTED]
Subject: Re: Clearing Expiry Messages
Set an Expiry just above your Wait Interval is valid, but keep in mind that
your queues will be cleared almost immediately of any orphaned messages as
subsequent gets execute. This
L PROTECTED]
Subject: Clearing Expiry Messages
Our developers ran across some documentation on expiration and have
began to implement their design to use this feature.
The are sending a questions to a remote queue manager and expect
a response in a timely manner. If they do not receive the response the
a
Our developers ran across some documentation on expiration and have
began to implement their design to use this feature.
The are sending a questions to a remote queue manager and expect
a response in a timely manner. If they do not receive the response the
application continues on. Since they are
13 matches
Mail list logo
