| Author |
Message
|
| rameshchukka |
 Posted: Mon Aug 24, 2015 10:35 am Post subject: not able to clear messages on queue and not able to delete Q |
 |
|
Novice
Joined: 11 Feb 2015
Posts: 11
|
Hi,
We have XMITQ and want to clear the messages from queue and delete the
queue
Actions taken:
1) stopped sender channel and changed XMITQ GET option to ENABLE, but
not able to clear messages.
2) Delete sender channel and tried the same , but not able to clear
messages
3) Changed XMITQ to Local queue, but not able to clear messages.
4) Deleted Queue data file , but not able to clear messages or delete
the queue
When I saw queue status, I saw UNCOM value is showing as 7, but queue
depth is zero. I saw input and output process count is zero.
I have restarted queue manager, reboot server, but still not able to
clear messages. Queue status is same.
Thanks,
Ramesh |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Mon Aug 24, 2015 11:06 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20768
Location: LI,NY
|
Your messages are stuck in an uncommitted transaction.
Check dspmqtrn -a to look at the transaction status.
See if you need to commit or rollback...
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| rameshchukka |
| Posted: Mon Aug 24, 2015 1:16 pm Post subject: |
|
|
Novice
Joined: 11 Feb 2015
Posts: 11
|
Hi,
I got the output with dspmqtrn -a command. but I am getting below error when I try to do commit or backed out.
output:
| Code: |
TranNum(0,75796972)
TRANSTATE(ACTIVE)
UOWLOGDA( ) UOWLOGTI( )
UOWSTDA(2015-08-24) UOWSTTI(16.09.25)
UOWLOG( )
EXTURID(XA_FORMATID[48801] XA_GTRID[0E445D389B13D35375B3]
XA_BQUAL[7765626C6F6769632E656A622E636F6E7461696E65722E4A4D53436F6E6E656374696F6E506F6C6C65722E52657175657374454A4238363333313630B995D8F4])
CONN(BEFED95502321D20)
PID(30643) TID(122253)
APPLTAG(weblogic.Server)
APPLDESC(WebSphere MQ Channel)
CHANNEL(TEST)
CONNAME(10.33.38.5)
QMURID(0.75796972)
USERID(lmemqm) |
[mqm@ut04012] /var/mqm/ $ rsvmqtrn -m TESTQM -b 0,75796972
AMQ7055: The transaction number is not recognized.
[mqm@ut04012] /var/mqm/ $ rsvmqtrn -m TESTQM -c 0,75796972
AMQ7055: The transaction number is not recognized
How can find the transactions related to the XMITQ ?
Thanks,
Rmesh |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Mon Aug 24, 2015 4:26 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9486
Location: US: west coast, almost. Otherwise, enroute.
|
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Aug 25, 2015 4:37 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20768
Location: LI,NY
|
As you can see this is an external transaction initiated by the WebLogic server. After a bounce, does the WebLogic server resume / complete/ rollback transactions in flight?
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| rameshchukka |
| Posted: Tue Aug 25, 2015 9:21 am Post subject: |
|
|
Novice
Joined: 11 Feb 2015
Posts: 11
|
Hi,
I tried with below option, still having same issue.
rsvmqtrn -m TESTQM -a
Didn't see any difference at transaction level after weblogic server bounce.
Thanks,
Ramesh |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Tue Aug 25, 2015 4:09 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9486
Location: US: west coast, almost. Otherwise, enroute.
|
| fjb_saper wrote: |
| As you can see this is an external transaction initiated by the WebLogic server. ... |
I blame alcohol for my misunderstanding.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Aug 25, 2015 6:50 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20768
Location: LI,NY
|
| rameshchukka wrote: |
Hi,
I tried with below option, still having same issue.
rsvmqtrn -m TESTQM -a
Didn't see any difference at transaction level after weblogic server bounce.
Thanks,
Ramesh |
Well after the bounce can you now resolve the transaction with -b or -c ?
I believe for that to work the transaction must have been in a specific state (prepare commit). Once the driving process is dead, (and not resurrected) you could potentially clear it by bouncing the qmgr (if the prepare commit was never issued)
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| rameshchukka |
| Posted: Thu Aug 27, 2015 8:08 am Post subject: |
|
|
Novice
Joined: 11 Feb 2015
Posts: 11
|
Hi,
I m not able to resolve the transactions using -b or -c after queue manager/server bounce.
Also I didn't see any output with below command
mqm@ut04010] /var/mqm/ $ dspmqtrn -m TESTQM -e -h -i
There are no matching prepared or heuristically completed transactions.
Thanks,
Rmesh |
|
| Back to top |
|
|
|
|
