| Author |
Message
|
| luzma |
 Posted: Fri Aug 24, 2007 12:59 am Post subject: messages duplicated in the queue |
 |
|
Newbie
Joined: 20 Nov 2006
Posts: 8
|
Which could be the cause that messages arrive duplicate in a queue ? I have a machine with MQ 5.2 on Solaris 8 and communicate with other macine with MQ 5.3 on solaris 10, but in the last days, in the mornig su one specific queue the same message arrive till 20 times 
I have controlled the logs but I haven't seen any problem of communication between the machines. Anyone hat any idea about which could be the problem ?
Thanks in advance,
Luz Marina |
|
| Back to top |
|
 |
| Vitor |
| Posted: Fri Aug 24, 2007 1:12 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Aside from MQv5.2 is way, way out of support and should have been upgraded ages back?
Are these true duplicates with the same message id, or the same message body put 20 times by a failing application?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Fri Aug 24, 2007 8:28 am Post subject: |
|
|
Guest
|
MQs primary function is to deliver a message ONCE and ONCE ONLY.
I'd look at the application program. |
|
| Back to top |
|
|
| luzma |
| Posted: Mon Aug 27, 2007 7:35 am Post subject: |
|
|
Newbie
Joined: 20 Nov 2006
Posts: 8
|
Many thanks for your answer, the application doesn't register the message Id, but indeed the application sent more than one time the same message, but I don't understand why, and why only lastly and in random way. This application has worked good for more than four years, since the last update of MQ to v. 5.2
For now We Can not update MQ because in this machine there are other applications that work with MQ and We can't update them because they will be changed soonly.
I was seeing the logs of MQ and I haven't seen any anomaly. Do you know if is possible to put a trace to one sepecific queue ? |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Aug 27, 2007 8:21 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| luzma wrote: |
| but I don't understand why, and why only lastly and in random way. This application has worked good for more than four years, since the last update of MQ to v. 5.2 |
Thus is the nature of application errors.
| luzma wrote: |
For now We Can not update MQ because in this machine there are other applications that work with MQ and We can't update them because they will be changed soonly. |
This is false reasoning. You shouldn't need to change the application programs when MQ is updated any more than you'd change them when you upgrade database software.
| luzma wrote: |
I was seeing the logs of MQ and I haven't seen any anomaly. Do you know if is possible to put a trace to one sepecific queue ? |
No. Tracing is an application function, and where I suspect you'll find the problem.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Mon Aug 27, 2007 11:03 am Post subject: |
|
|
Guest
|
| Let me guess: your application programmers are demanding that you prove duplicate/missing messages are NOT mq's fault before they look into their own programs and data. |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Aug 27, 2007 11:17 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| bruce2359 wrote: |
| Let me guess: your application programmers are demanding that you prove duplicate/missing messages are NOT mq's fault before they look into their own programs and data. |
Don't they always...... 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| sidharth_bora |
| Posted: Tue Aug 28, 2007 6:56 pm Post subject: |
|
|
Voyager
Joined: 24 Nov 2005
Posts: 87
|
Many thanks for your answer, the application doesn't register the message Id, but indeed the application sent more than one time the same message, but I don't understand why, and why only lastly and in random way. This application has worked good for more than four years, since the last update of MQ to v. 5.2
For now We Can not update MQ because in this machine there are other applications that work with MQ and We can't update them because they will be changed soonly.
I was seeing the logs of MQ and I haven't seen any anomaly. Do you know if is possible to put a trace to one sepecific queue ?
Hi Luzma,
probably you can configure an exit (sort of mirrorq) to the queue where the application is putting the message to and then analyze the received messages with the backed up in the mirror q. just my 20 cents on this problem |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Wed Aug 29, 2007 6:44 am Post subject: |
|
|
Guest
|
| Are the duplicated messages exact duplicates? Are the Message Descriptor PutDate and PutTime exactly the same? Or is it just the application data that is the same? |
|
| Back to top |
|
|
|
|
