|
Home > Archive > BizTalk Server > April 2007 > Biztalk Server 2006 Configuration
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 |
Biztalk Server 2006 Configuration
|
|
|
| I have exposed an orchestration as a web service. The HttpReceive Port
is a request-response port. In the orchestration I receive the message
search for a value and return the value. Sometimes this takes as long
as 20 seconds, The very next try it takes 2-3 seconds. I have changed
the HttpBatchSize on the receive handler of HTTP Adapter to 1. It
still takes the same time (The first time around).
Can someone tell me what I am missing?
Thanks
SJ
| |
| Alastair Grant 2007-03-26, 7:24 pm |
| IIS and BizTalk will unload their assemblies etc when it's been idle for
20 minutes or so. You need to set the Application Pool in IIS not to
shutdown after being idle.
You will also need to do this for the BizTalk Orchestration engine, this
is described in:
http://msdn2.microsoft.com/en-us/library/aa578610.aspx
But basically you need to add this to your BTSNTSvc.exe.config:
<configSections>
<section name="xlangs"
type="Microsoft.XLANGs.BizTalk.CrossProcess. XmlSerializationConfigurationSectionHand
ler,
Microsoft.XLANGs.BizTalk.CrossProcess" />
</configSections>
<xlangs>
<Configuration>
<AppDomains AssembliesPerDomain="10">
<DefaultSpec SecondsIdleBeforeShutdown="1200"
SecondsEmptyBeforeShutdown="1800" />
</AppDomains>
</Configuration>
</xlangs>
Please also note that I've witnessed BizTalk always taking 15 seconds to
respond to a web-service request on each new connection to the server,
no matter how little delay was left between calls. We never resolved
this issue and had a call open with Microsoft, who have not been able to
find a solution. We suspect this may have been to do with Windows Load
Balancing on 64-bit boxes. We are currently avoiding NLB.
Sree wrote:
> I have exposed an orchestration as a web service. The HttpReceive Port
> is a request-response port. In the orchestration I receive the message
> search for a value and return the value. Sometimes this takes as long
> as 20 seconds, The very next try it takes 2-3 seconds. I have changed
> the HttpBatchSize on the receive handler of HTTP Adapter to 1. It
> still takes the same time (The first time around).
>
> Can someone tell me what I am missing?
>
> Thanks
> SJ
>
| |
|
| Alaistar,
I had the same problem. The way we resolved is by reducing the worker
processes on the application pol. I think by default it is 1. But if
it is changed to a higher number it introduces some latency in the
calls to IIS.
HTH
Sree
On Mar 26, 6:21 pm, Alastair Grant <a...@for.it> wrote:
> IIS and BizTalk will unload their assemblies etc when it's been idle for
> 20 minutes or so. You need to set the Application Pool in IIS not to
> shutdown after being idle.
>
> You will also need to do this for the BizTalk Orchestration engine, this
> is described in:http://msdn2.microsoft.com/en-us/library/aa578610.aspx
>
> But basically you need to add this to your BTSNTSvc.exe.config:
>
> <configSections>
>
> <section name=3D"xlangs"
> type=3D"Microsoft.XLANGs.BizTalk.CrossProcess.XmlSerializationConfigurati=
onSe=ADctionHandler,
> Microsoft.XLANGs.BizTalk.CrossProcess" />
>
> </configSections>
>
> <xlangs>
>
> <Configuration>
>
> <AppDomains AssembliesPerDomain=3D"10">
>
> <DefaultSpec SecondsIdleBeforeShutdown=3D"1200"
> SecondsEmptyBeforeShutdown=3D"1800" />
>
> </AppDomains>
>
> </Configuration>
>
> </xlangs>
>
> Please also note that I've witnessed BizTalk always taking 15 seconds to
> respond to a web-service request on each new connection to the server,
> no matter how little delay was left between calls. We never resolved
> this issue and had a call open with Microsoft, who have not been able to
> find a solution. We suspect this may have been to do with Windows Load
> Balancing on 64-bit boxes. We are currently avoiding NLB. =20
>
>
>
> Sree wrote:
>
>
>
> - Show quoted text -
|
|
|
|
|