JMS Message resent for for long processes
843830Nov 21 2005 — edited Nov 23 2005Hi,
Currently we using Webspher App Server 6 and WSAD 6 as our development platform. We are also using Websphere MQ as our JMS server.
We have one MDB resposible for processing data extraction/migration jobs from legacy databases that can take anywhere from 20minutes to several hours to complete. Once the MDB receives the message, it starts the extraction process based on the information received in the message.
The problem is, once the job completes, it restarts again because the same message is resent to the MDB. Checking the value of getJMSRedelivered() from the message shows it is true the second time the message is received. I suspect the problem is the long time taken to execute the job, as when i test with a shorter job (1-2mins), the message is not resent. If the job takes approx more than 6mins, then the message is resent, but im not exactly sure of the actual time before the message is resent.
Im unsure where the problem lies. Currently i just check if the message is redelivered, and just ignore it, but this should not be the case, as redelivery is needed if there were any problems.
How do i avoid the redelivery? Where could the problem be ??
need help as im no expert on JMS :-)
Thanks.