| Author |
Message
|
| Ajju. |
 Posted: Wed Jul 31, 2002 12:52 pm Post subject: Message dies very soon !! |
 |
|
Voyager
Joined: 26 Jul 2002
Posts: 77
|
We are using a java program on the web-side and a natural program(program written in legacy language NATURAL) to communicate with legacy system.
now the problem is that natural progam is picking up the message form its inputQ and writting it back sucessfully to outputQ but the message dies before it is hitting NEON integrator..
Can anybody help me out of this .............
Ajit |
|
| Back to top |
|
 |
| bduncan |
| Posted: Wed Jul 31, 2002 4:06 pm Post subject: |
|
|
Padawan
Joined: 11 Apr 2001
Posts: 1554
Location: Silicon Valley
|
What exactly do you mean by "message dies" ???
Is the message expiring?
Is the MQPUT/MQGET failing, and if so, what reason code?
Is there anything in the queue manager logs?
Are there any FDCs being generated?
etc...
_________________
Brandon Duncan
IBM Certified MQSeries Specialist
MQSeries.net forum moderator |
|
| Back to top |
|
|
| Ajju. |
| Posted: Thu Aug 01, 2002 6:23 am Post subject: Message dies |
|
|
Voyager
Joined: 26 Jul 2002
Posts: 77
|
Hi,
Message dies means that i am able to put message sucessfuly on remoteQ using a NATURAL(its leagacy language) prgram and on the server i am able to see the message in the transmissionQ with the sender channel in stop mode.
This message then expires there in like 1-2 second even though the expire time is something like 999999
can you help me to identify that where are the locations where i can override the expiry time can be set..
Thanks !!
Ajit. |
|
| Back to top |
|
|
| bduncan |
| Posted: Thu Aug 01, 2002 9:51 am Post subject: |
|
|
Padawan
Joined: 11 Apr 2001
Posts: 1554
Location: Silicon Valley
|
You can't "override" the expiry time. Once it has been set for a message during the MQPUT, it is set in stone. That's not to say you can't remove the message from the queue, take the contents and create a new message, to effectively "reset" the expiry timestamp, but technically it's not the same message anymore.
Also, I'm not convinced the messages are expiring because messages don't expire on the transmission queues. It's not until an application comes along and attempts to get the message that it actually expires. In fact, expired messages still show up on the depth of the queue, so until something tries to get it, you should see a depth of 1.
_________________
Brandon Duncan
IBM Certified MQSeries Specialist
MQSeries.net forum moderator |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Thu Aug 01, 2002 9:56 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
I think the message is leaving the XMIT queue, but you don't see it where you thought it was going, so you assume it "died".
Look in your dead letter queues. It may have been thrown there.
Also just to clarify a little on what Brandon said. Messages can expire on an XMIT queue, just like any other local queue, but its not till an application goes to get on that queue (in the case of an XMIT q it is the MCA) that the QM will actually remove it and you see the Queue depth go down.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| Ajju. |
| Posted: Mon Aug 05, 2002 6:40 am Post subject: Thanks !! |
|
|
Voyager
Joined: 26 Jul 2002
Posts: 77
|
Thanks !! Brandon Duncan & Peter Potkay,
Got it working.. as it was wrongly triggering another process and the messages were getting disappeared .
Ajit. |
|
| Back to top |
|
|
|
|
