|
Home > Archive > BizTalk Server > October 2005 > MSMQT slow service instances when sending
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
MSMQT slow service instances when sending
|
|
| K Price 2005-08-19, 7:53 am |
| We have deployed our solution to a multi-server environment but are now often
seeing very long service instance execution times when sending to any MSMQT
send port.
The service instance of the send port in HAT indicates execution times of 30
seconds to 40 minutes. The send ports and corresponding receive locations use
the default Microsoft Xml pipelines.
Two of our BizTalk application servers are running the host containing the
MSMQT adapter, and there is a virtual IP address for the Altheon hardware
load balancer pointing to these two servers. The BizTalk application servers
are running network adapter teaming. We are addressing our send ports with
the TCP:[virtual IP address]\Private$\[QueueName] syntax from page 453 of
Scott's BizTalk book. We are running BTS SP 1.
Does anyone have any ideas? For example, does anyone know if hardware load
balancing is supported by MSMQT or is it only NLB? Any issues with the
adapter teaming? Any help greatly appreciated - thanks!
| |
| Paul Somers 2005-10-08, 2:48 am |
| Hi,
We have tried this, and then reverted back to a single BizTalk server
receiving messages. I prefer a clustered MSMQ server if possible for
redundancy.
What you are seeing is exactly what we had, remove load balancer, and it
works much better. I will not go into the detail, but it has got to do with
acks not going back to the machine that sent them.
Do you need ordered delivery? If not switch to MSMQC rather, it will be
faster to receive and send messages as it does not have the overhead of
MSMQT.
The other thing about MSMQT is it will stick to a single machine, even if
you have it running on two machines in the same host, each queue will stick
to the one machine and never cross that boundary.
Paul.
"K Price" <KPrice@discussions.microsoft.com> wrote in message
news:9D85B944-9107-4B9D-A152-D52193919AE2@microsoft.com...
> We have deployed our solution to a multi-server environment but are now
> often
> seeing very long service instance execution times when sending to any
> MSMQT
> send port.
>
> The service instance of the send port in HAT indicates execution times of
> 30
> seconds to 40 minutes. The send ports and corresponding receive locations
> use
> the default Microsoft Xml pipelines.
>
> Two of our BizTalk application servers are running the host containing the
> MSMQT adapter, and there is a virtual IP address for the Altheon hardware
> load balancer pointing to these two servers. The BizTalk application
> servers
> are running network adapter teaming. We are addressing our send ports with
> the TCP:[virtual IP address]\Private$\[QueueName] syntax from page 453 of
> Scott's BizTalk book. We are running BTS SP 1.
>
> Does anyone have any ideas? For example, does anyone know if hardware load
> balancing is supported by MSMQT or is it only NLB? Any issues with the
> adapter teaming? Any help greatly appreciated - thanks!
|
|
|
|
|