WebSphere MQ Persistence/non-persistence

I have a requirement to make a message non-persistent because it is not that important, My environment has WebsPhere Mq, Websphere application server,  and java application that is actually putting that message.

I have set the persistence/priority on the application server to use "as set in queue definiton", the queue definition is set to non-persistent. When the application team sends a message and we look at the header it appears to be persistent.

Does anybody know what I am missing and how can I make this message as non-persistent?
Who is Participating?
gheistConnect With a Mentor Commented:
You have to use Tuxedo (end application should set to use queue default)
Because it is set in application?
WASUser700Author Commented:
how do I change it to use what is set in the queue definiton?
Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

WASUser700Author Commented:
i.e tuxedo's queue definitions set message parameters, while in MQ it is done via client API
Set MQMD message persistence to  nonpersistent (MQPER_NOT_PERSISTENT) and your message will always retain that value.

MQPER_PERSISTENCE_AS_Q_DEF is the default setting for the persistence value in the MQMD.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.