| Author |
Message
|
| atheek |
 Posted: Sun Oct 15, 2006 7:34 pm Post subject: |
 |
|
Partisan
Joined: 01 Jun 2006
Posts: 327
Location: Sydney
|
There is nothing in AMQERR01.log to suggest that the queue is damaged!! Here is the message descriptor :
MQMD.Version 1
.MQMD.Report MQRO_NONE
.MQMD.MsgType MQMT_DATAGRAM
.MQMD.Expiry -1
.MQMD.Feedback ?2085?
.MQMD.Encoding MQENC_INTEGER_UNDEFINED+MQENC_INTEGER_NORMAL+MQENC_DECIMAL_UNDEFINED+MQENC_DECIMAL_NORMAL+MQENC_FLOAT_UNDEFINED+MQENC_FLOAT_IEEE_NORMAL
.MQMD.CodedCharSetId 819
.MQMD.Format MQDEAD
.MQMD.Priority 0
.MQMD.Persistence MQPER_PERSISTENT
.MQMD.MsgId 414D512042542E514D2E4C4C553236544422DBCA20007701
.MQMD.CorrelId 000000000000000000000000000000000000000000000000
.MQMD.BackoutCount 0
.MQMD.ReplyToQ
.MQMD.ReplyToQMgr QMA
.MQMD.UserIdentifier sundar5
.MQMD.AccountingToken 0532353232390000000000000000000000000000000000000000000000000006
.MQMD.ApplIdentityData
.MQMD.PutApplType MQAT_AIX
.MQMD.PutApplName MQIAPPL
.MQMD.PutDate 20061012
.MQMD.PutTime 13270909
.MQMD.ApplOriginData
here is the data:
DLH .......%ABCD......
................
................
................
................
...3 ....
................
................
............hell
o |
|
| Back to top |
|
 |
| atheek |
| Posted: Sun Oct 15, 2006 7:37 pm Post subject: |
|
|
Partisan
Joined: 01 Jun 2006
Posts: 327
Location: Sydney
|
| The other queue managers and the other queues under the same queue manager are working fine!! so cant suspect of any resource issue!! |
|
| Back to top |
|
|
| Mr Butcher |
| Posted: Sun Oct 15, 2006 9:58 pm Post subject: |
|
|
Padawan
Joined: 23 May 2005
Posts: 1716
|
as it has already been written before - if the queue really does not exist a 2085 should be returned from the amqsput. the msg should not go to the DLQ because MQ is able to give a returncode to the program (the DLQ is used in most cases for distributed queueing).
have you done any tests on that machine with distributed queueing and (maybe) now using the wrong queue or queuemanager?
please show us the output of 'dspmq'
please add the name of the queuemanager to the amqsput command. then use runmqsc with the same queuemanagername and check again that this is a QLOCAL
_________________
Regards, Butcher |
|
| Back to top |
|
|
| atheek |
| Posted: Sun Oct 15, 2006 10:13 pm Post subject: |
|
|
Partisan
Joined: 01 Jun 2006
Posts: 327
Location: Sydney
|
oops!! Now its working!!. ... i gave the same amqsput command as before .. now i can see the message in the queue..previously it was not there!! cant understand why its behaving as such!!  |
|
| Back to top |
|
|
| Mr Butcher |
| Posted: Sun Oct 15, 2006 10:43 pm Post subject: |
|
|
Padawan
Joined: 23 May 2005
Posts: 1716
|
i dont think that it is related to sun activity or earth ray, moste likely the problem sits on the keyboard  nevermind....
you should try to figure out what was wrong.
_________________
Regards, Butcher |
|
| Back to top |
|
|
| atheek |
| Posted: Sun Oct 15, 2006 11:36 pm Post subject: |
|
|
Partisan
Joined: 01 Jun 2006
Posts: 327
Location: Sydney
|
butcher,
I am sure the problem is not with keyboard!! I am still havin the message in the dead letter queue with the name dest queue name same as the local queue used. could you please explain how this is possible?? |
|
| Back to top |
|
|
| Mr Butcher |
| Posted: Mon Oct 16, 2006 12:08 am Post subject: |
|
|
Padawan
Joined: 23 May 2005
Posts: 1716
|
imho this problem can not occur with a "local" queuemanager and a "local" amqsput to a local queue.
in addition, why do you not anser the questions asked?
please show a "dspmq" of that machine
are there any other testers using this machine and qmgr?
did you perform any tests with distributed queueing or clustering before?
mq version?
_________________
Regards, Butcher |
|
| Back to top |
|
|
| atheek |
| Posted: Mon Oct 16, 2006 12:23 am Post subject: |
|
|
Partisan
Joined: 01 Jun 2006
Posts: 327
Location: Sydney
|
dspmq shows 20 queue managers including the one I am using in a running state!!
There are other users using the other queues that comes under this queue manager and we havent tried for any distributed queueing or clustering.
This seems like an intermittent problem..now 'n' then its working fine..but not all the time!! |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Oct 16, 2006 3:20 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20763
Location: LI,NY
|
| atheek wrote: |
dspmq shows 20 queue managers including the one I am using in a running state!!
There are other users using the other queues that comes under this queue manager and we havent tried for any distributed queueing or clustering.
This seems like an intermittent problem..now 'n' then its working fine..but not all the time!! |
20 qmgrs all on the same machine? Looks like a possible resource problem to me. 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Mr Butcher |
| Posted: Mon Oct 16, 2006 3:21 am Post subject: |
|
|
Padawan
Joined: 23 May 2005
Posts: 1716
|
maybe the derfault queuemanager is changed from time to time? when it is not wirking, and you try the amqsput with the name of YOUR queuemanager, does it work in that case?
_________________
Regards, Butcher |
|
| Back to top |
|
|
| atheek |
| Posted: Mon Oct 16, 2006 4:42 am Post subject: |
|
|
Partisan
Joined: 01 Jun 2006
Posts: 327
Location: Sydney
|
| There is no default queueu manager ...and all the time I was mentioning both the queueu name and queueu manager name in the amqsput call!! |
|
| Back to top |
|
|
| kevinf2349 |
| Posted: Mon Oct 16, 2006 5:41 am Post subject: |
|
|
Grand Master
Joined: 28 Feb 2003
Posts: 1311
Location: USA
|
What have IBM said?
It would seem that you have good cause to raise an APAR |
|
| Back to top |
|
|
| Nigelg |
| Posted: Mon Oct 16, 2006 7:28 am Post subject: |
|
|
Grand Master
Joined: 02 Aug 2004
Posts: 1046
|
Msgs do not get put to a DLQ if the put fails, the MQPUT returns an error. Msgs would get put to a DLQ if there were channels involved.
IBM will want to see a trace of the problem happening before they will believe that there is a problem.
Easily the most likely cause of the problem is user error.
_________________
MQSeries.net helps those who help themselves.. |
|
| Back to top |
|
|
| kevinf2349 |
| Posted: Mon Oct 16, 2006 8:02 am Post subject: |
|
|
Grand Master
Joined: 28 Feb 2003
Posts: 1311
Location: USA
|
| Quote: |
Easily the most likely cause of the problem is user error.
|
That would be my guess too, but they seem so insistent on that not being the case that I figured it must be a defect in the MQ code right  |
|
| Back to top |
|
|
| Nigelg |
| Posted: Tue Oct 17, 2006 12:12 am Post subject: |
|
|
Grand Master
Joined: 02 Aug 2004
Posts: 1046
|
Kevinf, you have your reasoning a little backward.
A function which works for everybody else, and is exercised millions of times a day, happens to go wrong for this particular person.
What is more likely, a defect in WMQ, or user error?
Also, don't forget that atheek is definitely wrong in saying that the msg goes to the DLQ when put to a local queue, that just does not happen.
So, the conclusion is:
1. atheek is not telling us everything
2. user error is the cause
_________________
MQSeries.net helps those who help themselves.. |
|
| Back to top |
|
|
|
|
