Multiple Processing of Messages

[Malcolm Sheldon]

Hi All,

I have just discovered a problem with a QC of mine which has been
working apparently correctly for about a year. However, under high
load conditions, it seems to process the same message multiple times.
I'm fairly sure that the remote system is not sending it multiple
times. As luck would have it one of the parameters, is the DateTime
of when the message is created by the remote system, and the messages
given to the receiver have the same timestamp.

So, I'm wondering if there is any way that MSMQ and/or Component
Services can manage to hand a message to the component without
removing it from the queue, so that it can be passed on again some
time later?

The time between messages seems variable, I'm looking at an example
where the first interation begins at 18:55:34, and before this
completes another thread starts up at 19:00:30 to process the message
again, then a third thread starts at 19:00:55 with the same message.
The first thread doesnt complete until 19:01:55.

I wondered if there was some sort of timeout going on, which says
something like, "If the message hasnt been processed within x secs
then give it another try"

Maybe MSMQ is moving the message into the next queue down, heading for
the dead letter queue??

The receiving system is W2K Server, the sending systems are XP-Pro,
and the queues are set up in Workgroup mode using IP addresses to
target the receiver.

Any ideas guys???

Many Thanks

Malcolm Sheldon

[Doron Juster [MSFT]]

If for some reason the transaction gets aborted the message will end up on a
retry queue. We will retry 16 times till we give up on the message. In this
case it seems like this transaction is timing out.

I'd suggest you followup with this on the
microsoft.public.platformsdk.complus_mts or
microsoft.public.dotnet.framework.component_services

newgroups which are more appropriate for COM+ and QC related questions.
thanks, Doron
--
This posting is provided "AS IS" with no warranties, and confers no rights.
.

"Malcolm Sheldon" <bnch...@ozemail.com.au> wrote in message
news:50356c40.04041...@posting.google.com...