| Author |
Message
|
| skrv |
 Posted: Wed Oct 31, 2012 5:46 pm Post subject: How to make MQ Message as Non-Persistent and set some Expiry |
 |
|
Centurion
Joined: 26 Oct 2012
Posts: 118
|
We have an Application developer who is using JMS MQ API to send messages to MQ Infrastructure. The problem is he is putting messages as "Persistent" and "Non-Expiry". In our Infrastructure the standard is MQ Messages should be "Non-Persistent" and should have some expiry value. He is trying for so many days but he is not able to identify what parameters that need to be altered so that messages are put to MQ as Non-Persistent and have some expiry.
I'm an MQ Admin and i don't know the developing part of it. So It would be very helpful if some one can suggest what exactly needs to be changed in JMS MQ API to have MQ messages changed to Non-Persistent and with Some Expiry.
Current MQ Header:
-------------------------------------
Message Descriptor (MQMD)
StrucId :'MD '
Version :1
Report :00000000
Message Type :1 (Request msg)
Expiry :-1 ----------------------------> (-1) Non-Expiring message
Feedback :0 (None)
MQEncoding :0x'111'
CCSID :1208
Format :'MQHRF2 '
Priority :4
Persistence :1 (Persistent)----------------> Persistent message.
--------------------------------------
MQ Header We Want:
--------------------------------------
Message Descriptor (MQMD)
StrucId :'MD '
Version :1
Report :00000000
Message Type :1 (Request msg)
Expiry :2234 ----------------------> Message will expire
Feedback :0 (None)
MQEncoding :0x'111'
CCSID :819
Format :'MQHMDE '
Priority :4
Persistence :0 (Not Persistent)--------> Non-Persistent message.
--------------------------------------------
Any help would be greatly appreciated.
thanks
skrv |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Wed Oct 31, 2012 7:53 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20763
Location: LI,NY
|
In JMS the persistency attribute is set on the destination. The TTL (time to live) is set by using a more complicate send interface of the producer.
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| zpat |
| Posted: Thu Nov 01, 2012 12:44 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5867
Location: UK
|
You need to careful about saying the standard is always "non-persistent".
It will depend upon each application and whether they expect the message to be recovered in the event of a queue manager failure or not. |
|
| Back to top |
|
|
| skrv |
| Posted: Thu Nov 01, 2012 12:00 pm Post subject: |
|
|
Centurion
Joined: 26 Oct 2012
Posts: 118
|
yes, this is not standard for all kinds of messages and also varies by application. I thought i was referring to this particular issue in hand.
Thanks for the reply. |
|
| Back to top |
|
|
| searchjoe |
| Posted: Sun Aug 10, 2014 5:27 pm Post subject: |
|
|
Newbie
Joined: 10 Aug 2014
Posts: 1
|
| You can set it on the producer application's java api code using TimeToLive method or You can also try on the Application server(Resources/Qeues) |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Sun Aug 10, 2014 9:47 pm Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
searchjoe,
Welcome to this forum.
However what was really gained by reopening an almost 2year old thread with your post.
The subject of the thread is not exactly a hot topic here so should have probably remained dormant until someone else asked about it. Then you could have supplied your answer at that point.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
|
|
