Hi,

I'm currently shining a flashlight into the great dark known as
"MSMQT".   I'm having some success and things are going well but I have
one big question.

Why can none of my MS-supplied tools connect to a Private queue on the
local machine?   I have used LoadGen and SendLargeMessage and both
exhibit the same problem where if you point them to the local machine
they crap out.  However, using exactly the same settings they work
great if i point them at a different machine.  I can reproduce this
behaviour on two machines (with an unconfirmed third exhibiting similar
behaviour).  The machines are Windows2003 VPC's running BTS 2004, sql
2000, etc.

Is there some unspoken rule that MSMQT only works remotely?

As an additional confusion, when I configure a receive port to pick up
a file and configure another send port to listen for that port and pass
the file 'messsage' to an MSMQT queue it works.  I'm not sure why BTS
can talk to MSMQT remotely but it does work.

Can anyone shed light on this for me?

Thanks in advance,

[ Post a follow-up to this message ]

Karlid,

> I'm currently shining a flashlight into the great dark known as
> "MSMQT".   I'm having some success and things are going well but I have
> one big question.
>
> Why can none of my MS-supplied tools connect to a Private queue on the
> local machine?   I have used LoadGen and SendLargeMessage and both
> exhibit the same problem where if you point them to the local machine
> they crap out.  However, using exactly the same settings they work
> great if i point them at a different machine.  I can reproduce this
> behaviour on two machines (with an unconfirmed third exhibiting similar
> behaviour).  The machines are Windows2003 VPC's running BTS 2004, sql
> 2000, etc.
>
> Is there some unspoken rule that MSMQT only works remotely?
>
> As an additional confusion, when I configure a receive port to pick up
> a file and configure another send port to listen for that port and pass
> the file 'messsage' to an MSMQT queue it works.  I'm not sure why BTS
> can talk to MSMQT remotely but it does work.

Are you running MSMQT and MSMQ side by side? there are a few bugs related to
that, btw.
Also, when you connect locally, are you using the machine's public IP
address/name, or are you resolving to 127.0.0.1? I believe the latter might
cause trouble, though I'm not 100% sure on that.



--
Tomas Restrepo
tomasr@mvps.org
http://www.winterdom.com/

[ Post a follow-up to this message ]

Yes, we are running both MSMQ and MSMQT concurrently on the same
server.  They are bound to separate IP addresses as advised by the
documentation.  Do you have more information on the bugs you mention?
Since this is a pilot project for a much larger solution I'd like to be
sure none of them are job-stoppers!

For connecting locally we have tried both machine name and ip address.
I have not tried the local IP (127.0.0.1) but only the public IP.

Any thoughts?  It seems strange to me that three machines would all
have the same problem if it was just a configuration issue.  Of course,
having said that I'm the common denominator so maybe the problem is me!


Tomas Restrepo (MVP) wrote:
> Are you running MSMQT and MSMQ side by side? there are a few bugs related 
to
> that, btw.
> Also, when you connect locally, are you using the machine's public IP
> address/name, or are you resolving to 127.0.0.1? I believe the latter migh
t
> cause trouble, though I'm not 100% sure on that.
>
>
>
> --
> Tomas Restrepo
> tomasr@mvps.org
> http://www.winterdom.com/

[ Post a follow-up to this message ]

Karlid,

> Yes, we are running both MSMQ and MSMQT concurrently on the same
> server.  They are bound to separate IP addresses as advised by the
> documentation.  Do you have more information on the bugs you mention?
> Since this is a pilot project for a much larger solution I'd like to be
> sure none of them are job-stoppers!

In theory, they are fixed, though I have to admit I didn't have much work in
getting it to work very reliably. Here are the relevant KB articles:

http://support.microsoft.com/?kbid=873385
http://support.microsoft.com/kb/873322/

While not directly related, these might be useful, as well:
http://support.microsoft.com/?scid=...pid=1444&sid=90
http://support.microsoft.com/?kbid=901268


--
Tomas Restrepo
tomasr@mvps.org
http://www.winterdom.com/

[ Post a follow-up to this message ]

Thanks for the links.  I will digest.

So, am I correct in assuming that this problem of not being able to
connect to the local queues is not how it's *supposed* to work?

[ Post a follow-up to this message ]

Karlid,

> Thanks for the links.  I will digest.
>
> So, am I correct in assuming that this problem of not being able to
> connect to the local queues is not how it's *supposed* to work?

I don't think it was intentional, if that was what you meant, but my
experience seems to suggest it just doesn't always work.

Also, you might want to make the biztalk threading pool larger... the MSMQ
and MSMQT adapters are notorious for how many threads they use, which might
be worsening the issue. Here's some information on that from Scott
Colestock:
http://www.traceofthought.net/Perma...22.
aspx


--
Tomas Restrepo
tomasr@mvps.org
http://www.winterdom.com/

[ Post a follow-up to this message ]