Messages stuck in outgoing queue

Eddie Davis

unread,

Jun 18, 2003, 2:47:49 PM6/18/03

to

I have several messages sitting in an outgoing queue.
Periodically the state will change to Connect and the Next
hop shows the IP address of the correct server the
messages should be sent to. I have tried to restart the
MSMQ service with no luck. Where can I look to determine
why the messages are stuck? Any help would be appreciated.

Emmanuel Dreux [MSFT]

unread,

Jun 19, 2003, 7:11:29 AM6/19/03

to

Are they transactional or not?

As a starting point, in the outgoing queues, look at the counters :
messages, unacked and unprocessed messages.
Are there unacked or unprocessed messages?
This would mean that the messages have been sent but the sender didn't
receive acknowledgments or the application on the destination side didn't
consume the messages.

A good solution would be to perform a network trace between the client and
the server and have it analysed by Microsoft support.

Regards,
Emmanuel.

"Eddie Davis" <jed...@gapac.com> a écrit dans le message de news:
031101c335ca$1d73a550$a301...@phx.gbl...

Eddie Davis

unread,

Jun 20, 2003, 9:50:30 AM6/20/03

to

The messages shows 629 (gradually rises during the day),
the unacked shows 0 messages, and the unprocessed shows
629 messages. So does this mean the application on the
destination side didn't consume the message? Where can I
look to see why?

Thanks in advance for your help!

>.
>

Eddie Davis

unread,

Jun 20, 2003, 11:08:43 AM6/20/03

to

Also the messages are transactional.

>.
>

Emmanuel Dreux [MSFT]

unread,

Jun 23, 2003, 8:57:23 AM6/23/03

to

So does this mean the application on the destination side didn't consume the
message?

--> yes, exactly.

Check the event log and verify if your application logged something ( VB
runtime error, com+ error....),
if it's a com+ application, verify it's started...

You might need to involve the developer of your application to figure out
why it's not consuming messages ( add logging, debug the app...)

Thanks,
Emmanuel Dreux.
This posting is provided "AS IS" with no warranties, and confers no rights.

"Eddie Davis" <jed...@gapac.com> a écrit dans le message de news:

05f001c33732$e9741fe0$a001...@phx.gbl...

Srinath Remala

unread,

Aug 13, 2003, 10:22:13 AM8/13/03

to

The messages are not reaching the destination queue. We
can see the 'notprocessed' counter in Outgoing Queues (on
the sender machine) incrementing for each new message.

We tried 1) deleting the queue and recreating
2) able to send to the same desitnation queue
from a different machine.
On a rleated note,
Is there any way to monitor/access the Outgoing queue on
a regular basis, programatically? That will help us in
identifying if the problem occurs again.

>.
>

Doron Juster [MSFT]

unread,

Aug 17, 2003, 5:15:55 AM8/17/03

to

The "unprocessed" counter tells you how many transactional messages reached
destination queue but were not yet received. Please refer to
http://www.microsoft.com/windows2000/technologies/communications/msmq/wp_msmqfaq.asp,
"administration FAQ", item #12 for more details. See also discussion at
http://msdn.microsoft.com/library/en-us/msmq/msmq_about_transactions_8y7n.asp .

You can use the local admin api
(http://support.microsoft.com/default.aspx?kbid=242471 ) to monitor outgoing
queues. This API has a COM interface on msmq3.0 (WinXP and Win2003).

Thanks, Doron
--

This posting is provided "AS IS" with no warranties, and confers no rights.

.

"Srinath Remala" <sre...@gapac.com> wrote in message
news:07c301c361a6$4a6982c0$a001...@phx.gbl...