| Author |
Message
|
| jeevan |
 Posted: Sun Oct 15, 2006 7:27 am Post subject: Non persistant Message lived after rebooting queu emanager |
 |
|
Grand Master
Joined: 12 Nov 2005
Posts: 1432
|
According to my client, one of their transmission queues has some stranged message. They try to delete, it gives them 2016t erros which is get disabled. The amazing thing is that these are non persistant message and they lived after boucing the queue manager.
Is there any special thing with trasmission queue? why the message lived after bluncing the queue manager? why they can not be deleted? Any insight would be very helpful.
Thanks |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Sun Oct 15, 2006 8:17 am Post subject: |
|
|
Guest
|
A new feature to MQ is the queue attribute NPMCLASS.
NPMCLASS(HIGH) - This setting enables non-persistent messages on
this queue to be retained across a queue manager restart.
Non-persistent messages may still be lost in the event of a
failure.
NPMCLASS(NORMAL) - This is the default value and indicates
that non-persistent messages on this queue are only lost following
a failure, or a queue manager shutdown. These messages will be
discarded in the event of a queue manager restart.
Check your transmission queue for this attribute.
Given the risk of loss of non-persistent messages after a system failure (crash), do non-persistent messages make sense for your business application? |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sun Oct 15, 2006 10:30 am Post subject: Re: Non persistant Message lived after rebooting queu emanag |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| jeevan wrote: |
According to my client, one of their transmission queues has some stranged message. They try to delete, it gives them 2016t erros which is get disabled. The amazing thing is that these are non persistant message and they lived after boucing the queue manager.
Is there any special thing with trasmission queue? why the message lived after bluncing the queue manager? why they can not be deleted? Any insight would be very helpful.
Thanks |
Have you checked that they do not originate in a transaction that was aborted?(never rolled back never committed). Check the runmqt* commands there is something about displaying such transactions and resolving them...
The 2016 error is standard. When you stop the channel the get is disabled on the xmitq as a security feature (only the channel is supposed to get from an xmitq). You have to manually enable it if you want to browse or get messages from it.
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| jeevan |
| Posted: Sun Oct 15, 2006 2:53 pm Post subject: |
|
|
Grand Master
Joined: 12 Nov 2005
Posts: 1432
|
I will definitely update once I talked to the client. The problem is I am consultant - I am not allowed to hook with system, I have to provide the solution to whatever problem they have. Enough strange!!!!!!!!!
What else may I ask to check them. The error message as I have been told is queue in use. When i asked to shutdown and delete the message before connecting the application. their response is the same. Can I happen? doe the message in xtimq has such feature? I have never had this.
Any idea would be really helpful. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Sun Oct 15, 2006 4:31 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
An xmit queue is in use and get-disabled whenever the channel is running.
You can either have the client explicitly stop the channel, or you can have them manually get-enable the xmit queue, and then use something that issues MQGETs to clear the queue.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Oct 16, 2006 3:09 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
If the channel is running but the message does not get consumed and survives a qmgr restart, my guess is it might be a persistent message from an XA transaction that has not been committed but had a commit prepare issued against it. (blow up of the JVM or bad XA coordinator (ATG old versions))
runmqtrm should show you something...
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
