| Author |
Message
|
| pravin |
 Posted: Mon Jul 18, 2005 12:47 am Post subject: Data Missing - Strange |
 |
|
Newbie
Joined: 17 Jul 2005
Posts: 4
|
We have a mainframe system to write data into queue which is read by a java application.
The first record written into the queue is lost most of the times. If we write data when there is atleast one record the problem donot occur.
Does anybody have any idea abt this sitauation ???
Thanks
Pravin |
|
| Back to top |
|
 |
| Mr Butcher |
| Posted: Mon Jul 18, 2005 1:08 am Post subject: |
|
|
Padawan
Joined: 23 May 2005
Posts: 1716
|
whenever i saw something like this, it was a matter of the application.
try to test the writing and reading applications seperate. write first, then check the queue content, after that read the queue.
_________________
Regards, Butcher |
|
| Back to top |
|
|
| pravin |
| Posted: Mon Jul 18, 2005 1:15 am Post subject: |
|
|
Newbie
Joined: 17 Jul 2005
Posts: 4
|
Thanks yaar
can u pls let me know if there are any tools availabe to view the queue content.
When we write the first data into queue, the queue depth becomes one.
But just before the second write its turns to zero again.
For other writes it is incremented correclty.
Any idea wht the problem culd be |
|
| Back to top |
|
|
| Mr Butcher |
| Posted: Mon Jul 18, 2005 1:19 am Post subject: |
|
|
Padawan
Joined: 23 May 2005
Posts: 1716
|
for tools check the mqseries support pac page and google. mo71 is fine if you have a windows machine available, if not chose something else.
also the supplied samples may work (amqsbcg and so on).
is the write program the only programm serving the queue at this moment? no reading process? no queue triggering? make the queue get-disable, turn trigger off, then put the message. if it still disapears the writing program may be in error.
check the logs, fdc files and so on.
_________________
Regards, Butcher |
|
| Back to top |
|
|
| pravin |
| Posted: Mon Jul 18, 2005 2:58 am Post subject: |
|
|
Newbie
Joined: 17 Jul 2005
Posts: 4
|
| i am a new user of this site..pls let me know where the program mentioned <amqsbcg > is available??? |
|
| Back to top |
|
|
| sebastianhirt |
| Posted: Mon Jul 18, 2005 3:18 am Post subject: |
|
|
Yatiri
Joined: 07 Jun 2004
Posts: 620
Location: Germany
|
| Quote: |
| let me know where the program mentioned <amqsbcg > is available??? |
This is a free sample program that comes with your MQ installation.
Please check out the quick beginings for your platform, to get more information. |
|
| Back to top |
|
|
| JohnRodey |
| Posted: Mon Jul 18, 2005 5:07 am Post subject: |
|
|
Centurion
Joined: 13 Apr 2005
Posts: 103
|
Are you killing your Java application abnormally?
If you are I have noticed a issue with this. The application registers itself with the QM and tells it that it will be waiting for messages for X amount of time (specified by your wait interval). If you control-c that application (or kill it any other way abnormal way) the QM will still think that the Java app is still out there and will try sending the first message passed in to that application. Since that app is obviously not going to receive that message, it becomes lost. So if you wait interval on that app is infinite then the first message will be lost, if your wait was for 10 seconds then if a message comes in within that 10 seconds it will be lost, otherwise it will be fine.
This sort of issue can also be seen by queues that are exclusive, such as the default performance queue. If you have a queue that is exclusive and being monitored by an application that waits forever for a message, if that application is killed then the queue will not be able to give out any other handles to other apps wishing to get() from that queue, since the queue still thinks that application is out there.
I speak only of ver 5.3, Haven't tried ver 6.0 yet.
I have talked to IBM about this and they said that this behavior is expected. Not sure why they do not consider this a bug? Has anyone else seen this behavior? |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Jul 18, 2005 12:55 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Have you tried checking the queue for uncommitted msgs (assuming syncpoint) ?
Have your run dspmqtrn -m <qmgr> ?
 |
|
| Back to top |
|
|
| bower5932 |
| Posted: Mon Jul 18, 2005 2:03 pm Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
| JohnRodey wrote: |
| I have talked to IBM about this and they said that this behavior is expected. Not sure why they do not consider this a bug? Has anyone else seen this behavior? |
I've seen this behavior with client programs. The agent will be running on the server waiting for a message. I then kill my program and the agent is still waiting for a message. The message comes in. The agent attempts to send it to the client program and realizes it has gone away. If I was doing things outside of syncpoint, the message gets tossed. If it is inside of syncpoint, the message gets rolled back onto the queue. |
|
| Back to top |
|
|
| pravin |
| Posted: Tue Jul 26, 2005 4:22 am Post subject: |
|
|
Newbie
Joined: 17 Jul 2005
Posts: 4
|
thanks for the suggestions...
I downloaded a tool from net and checked the data in my queue.
I am not able to view the first data I write into queue.
while the successive records donot have any problem.
Once the data in queue is deleted my second PUT donot give this problem.
Any idea where the problem could be.
(I donot use commit or Syncpoint in my program) |
|
| Back to top |
|
|
| RogerLacroix |
| Posted: Tue Jul 26, 2005 6:27 am Post subject: |
|
|
Jedi Knight
Joined: 15 May 2001
Posts: 3264
Location: London, ON Canada
|
Hi,
Check your code and if you cannot find the problem then post it here (use BBCodes - paste your code then highlight the code and click the Code button.)
Regards,
Roger Lacroix
_________________
Capitalware: Transforming tomorrow into today.
Connected to MQ!
Twitter |
|
| Back to top |
|
|
|
|
