Hi, whne I try to do performance testing for Biztalk Server 2004, I call the
 orchestrations using 10 threads at a time, but it doesn't seem that Biztalk
 is running more than two orchestrations at the same time, which means that 
only two of my threads are
getting responses at the same instance.
Is there a way to increase the number of running messages at a time????

Thnx

[ Post a follow-up to this message ]

How exactly do you call your orchestration please?
The only correct way to do stress testing is probably by using the BizTalk
WMI perf counters.  It's not because you get results slower that only two
orchestrations run at the same time.

Kind regards,
Christof

"MohammadSH" <anonymous@discussions.microsoft.com> wrote in message
news:10F4A9F9-EA4E-4629-AB40-34DD0698AD90@microsoft.com...
>
> Hi, whne I try to do performance testing for Biztalk Server 2004, I call
the orchestrations using 10 threads at a time, but it doesn't seem that
Biztalk is running more than two orchestrations at the same time, which
means that only two of my threads are getting responses at the same
instance.
> Is there a way to increase the number of running messages at a time????
>
> Thnx

[ Post a follow-up to this message ]

they are exposed as web services, i use multi threading to call the web serv
ice, but no matter how many threads I use only two are being process by bizt
alk at a time

"Christof" wrote:

> How exactly do you call your orchestration please?
> The only correct way to do stress testing is probably by using the BizTalk
> WMI perf counters.  It's not because you get results slower that only two
> orchestrations run at the same time.
>
> Kind regards,
> Christof
>
> "MohammadSH" <anonymous@discussions.microsoft.com> wrote in message
> news:10F4A9F9-EA4E-4629-AB40-34DD0698AD90@microsoft.com... 
> the orchestrations using 10 threads at a time, but it doesn't seem that
> Biztalk is running more than two orchestrations at the same time, which
> means that only two of my threads are getting responses at the same
> instance. 
>
>
>

[ Post a follow-up to this message ]

Did you check with the BizTalk Server Perf counters please?

Kind regards,
Christof

"MohammadSH" <MohammadSH@discussions.microsoft.com> wrote in message
news:2C8CA8AD-B405-4CBA-B1E9-4DA9EB4DE1D8@microsoft.com...
> they are exposed as web services, i use multi threading to call the web
service, but no matter how many threads I use only two are being process by
biztalk at a time[vbcol=seagreen]
>
> "Christof" wrote:
> 
BizTalk[vbcol=seagreen] 
two[vbcol=seagreen] 
call[vbcol=seagreen] 
time????[vbcol=seagreen] 

[ Post a follow-up to this message ]

yes i did, and i eventually noticed a bizzare behaviour. when i create ten t
hreads in my application i only get a max of 2 running orchestrations (in th
e perf counters), but when i create ten instances of my application (one thr
ead in each) i can get up t
o 8 running orchestrations!!!!!!!!!!!

"Christof" wrote:

> Did you check with the BizTalk Server Perf counters please?
>
> Kind regards,
> Christof
>
> "MohammadSH" <MohammadSH@discussions.microsoft.com> wrote in message
> news:2C8CA8AD-B405-4CBA-B1E9-4DA9EB4DE1D8@microsoft.com... 
> service, but no matter how many threads I use only two are being process b
y
> biztalk at a time 
> BizTalk 
> two 
> call 
> time???? 
>
>
>

[ Post a follow-up to this message ]

You might be hitting the .NET thread pool limit.
To be very sure you should check the IIS log: how many requests you make in
what timespan.  (Regardless the amount of threads...  No thread ever calls
into BizTalk Server directly!)

Kind regards,

Christof

"MohammadSH" <MohammadSH@discussions.microsoft.com> wrote in message
news:0377A05C-4DFC-428B-959C-87566EE4E5BF@microsoft.com...
> yes i did, and i eventually noticed a bizzare behaviour. when i create ten
threads in my application i only get a max of 2 running orchestrations (in
the perf counters), but when i create ten instances of my application (one
thread in each) i can get up to 8 running  orchestrations!!!!!!!!!!![vbcol=seagreen
]
>
> "Christof" wrote:
> 
web[vbcol=seagreen] 
by[vbcol=seagreen] 
only[vbcol=seagreen] 
I[vbcol=seagreen] 
that[vbcol=seagreen] 
which[vbcol=seagreen] 

[ Post a follow-up to this message ]

you are most likely running into a throttle on outbound web requests.  This
is on a application domain level so that would explain why you don't see the
same behavior with multiple instances of you application.  Look in the
system.net configuration in your machine.config.  You'll find an entry for
MaxConnections.  Remember, this is per application pool and can be set on an
IP/host basis.

Matt


"Christof" <bts2004communityfeedback (at) hotmail (dot) com> wrote in
message news:O3CspRyTEHA.1984@TK2MSFTNGP12.phx.gbl...
> You might be hitting the .NET thread pool limit.
> To be very sure you should check the IIS log: how many requests you make
in
> what timespan.  (Regardless the amount of threads...  No thread ever calls
> into BizTalk Server directly!)
>
> Kind regards,
>
> Christof
>
> "MohammadSH" <MohammadSH@discussions.microsoft.com> wrote in message
> news:0377A05C-4DFC-428B-959C-87566EE4E5BF@microsoft.com... 
ten[vbcol=seagreen]
> threads in my application i only get a max of 2 running orchestrations (in
> the perf counters), but when i create ten instances of my application (one
> thread in each) i can get up to 8 running orchestrations!!!!!!!!!!! 
> web 
process[vbcol=seagreen]
> by 
> only 
message[vbcol=seagreen] 
2004,[vbcol=seagreen]
> I 
> that 
> which 
same[vbcol=seagreen] 
>
>

[ Post a follow-up to this message ]

Thanks for the info Math.
Nice to know!

Regards
Christof

"Matt Milner" <matt.milner@m3technologypartners dot com> wrote in message
news:%23r62wh1TEHA.204@TK2MSFTNGP10.phx.gbl...
> you are most likely running into a throttle on outbound web requests.
This
> is on a application domain level so that would explain why you don't see
the
> same behavior with multiple instances of you application.  Look in the
> system.net configuration in your machine.config.  You'll find an entry for
> MaxConnections.  Remember, this is per application pool and can be set on
an
> IP/host basis.
>
> Matt
>
>
> "Christof" <bts2004communityfeedback (at) hotmail (dot) com> wrote in
> message news:O3CspRyTEHA.1984@TK2MSFTNGP12.phx.gbl... 
> in 
calls[vbcol=seagreen] 
> ten 
(in[vbcol=seagreen] 
(one[vbcol=seagreen] 
the[vbcol=seagreen] 
> process 
the[vbcol=seagreen] 
> message 
> 2004, 
seem[vbcol=seagreen] 
time,[vbcol=seagreen] 
> same 
>
>

[ Post a follow-up to this message ]

thnx, it worked
i never thought that would be the case, we have tried changing it on the ser
ver, but we never thought it would be from the client
to be honest i thought it was changed in the client so i didn't check it out
thnx again, that's what seperates the pros from the the intermediates

Mohammad

"Matt Milner" wrote:

> you are most likely running into a throttle on outbound web requests.  Thi
s
> is on a application domain level so that would explain why you don't see t
he
> same behavior with multiple instances of you application.  Look in the
> system.net configuration in your machine.config.  You'll find an entry for
> MaxConnections.  Remember, this is per application pool and can be set on 
an
> IP/host basis.
>
> Matt
>
>
> "Christof" <bts2004communityfeedback (at) hotmail (dot) com> wrote in
> message news:O3CspRyTEHA.1984@TK2MSFTNGP12.phx.gbl... 
> in 
> ten 
> process 
> message 
> 2004, 
> same 
>
>
>

[ Post a follow-up to this message ]