BizTalk Server Applications Integration - Releasing system resources?

This is Interesting: Free IT Magazines  
Home > Archive > BizTalk Server Applications Integration > April 2004 > Releasing system resources?





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 Releasing system resources?
Rich Wallace

2004-04-14, 3:34 pm

Hi all,

I have several .NET based components (DLLs) being called from most of my
XLANG schedules. I've noteid that over time, the DLLHOST.EXE that is
hosting the XLANG Scheduler application consumes a large amount of memory
and if it reaches a level of say 800M, my components crash and I receive
Obect Reference errors from my components until I restart the XLANG Schedule
application.

If my DLLs are technicall 'running' within the DLLHOST.EXE, how can I mange
my memory consumption or clean up the resources I use between each call from
the XLANG? Any examples or best practice suggestion would be truly
apprecaited.

TIA
-Rich


Christof

2004-04-14, 3:34 pm

?

Is dllhost.exe hosting your schedules? Normally this should be
BtsNtSvc.exe. Can you explain please? (Or are you using biztalk server
2002? Then this makes sense...)

Regards,
Christof

"Rich Wallace" <rich.wallace@minusthecannedmeat.jfsheadotcom> wrote in
message news:OylYVQXIEHA.3040@TK2MSFTNGP09.phx.gbl...
> Hi all,
>
> I have several .NET based components (DLLs) being called from most of my
> XLANG schedules. I've noteid that over time, the DLLHOST.EXE that is
> hosting the XLANG Scheduler application consumes a large amount of memory
> and if it reaches a level of say 800M, my components crash and I receive
> Obect Reference errors from my components until I restart the XLANG

Schedule
> application.
>
> If my DLLs are technicall 'running' within the DLLHOST.EXE, how can I

mange
> my memory consumption or clean up the resources I use between each call

from
> the XLANG? Any examples or best practice suggestion would be truly
> apprecaited.
>
> TIA
> -Rich
>
>



Christof

2004-04-14, 3:34 pm

If you use interop, make sure you call the Marshaller.ReleaseCOMObject.
(Expecially true when using MSXML4 for some reason.)


"Rich Wallace" <rich.wallace@minusthecannedmeat.jfsheadotcom> wrote in
message news:OylYVQXIEHA.3040@TK2MSFTNGP09.phx.gbl...
> Hi all,
>
> I have several .NET based components (DLLs) being called from most of my
> XLANG schedules. I've noteid that over time, the DLLHOST.EXE that is
> hosting the XLANG Scheduler application consumes a large amount of memory
> and if it reaches a level of say 800M, my components crash and I receive
> Obect Reference errors from my components until I restart the XLANG

Schedule
> application.
>
> If my DLLs are technicall 'running' within the DLLHOST.EXE, how can I

mange
> my memory consumption or clean up the resources I use between each call

from
> the XLANG? Any examples or best practice suggestion would be truly
> apprecaited.
>
> TIA
> -Rich
>
>



Rich Wallace

2004-04-14, 3:34 pm

Sorry, using BTS2002.

"Christof" <bts2004communityfeedback (at) hotmail (dot) com> wrote in
message news:uhP$k2XIEHA.700@TK2MSFTNGP09.phx.gbl...
> ?
>
> Is dllhost.exe hosting your schedules? Normally this should be
> BtsNtSvc.exe. Can you explain please? (Or are you using biztalk server
> 2002? Then this makes sense...)
>
> Regards,
> Christof
>
> "Rich Wallace" <rich.wallace@minusthecannedmeat.jfsheadotcom> wrote in
> message news:OylYVQXIEHA.3040@TK2MSFTNGP09.phx.gbl...
memory[color=darkred]
> Schedule
> mange
> from
>
>



Rich Wallace

2004-04-14, 3:34 pm

We've created our components using the ProcessMessage function implementing
IBTSAppIntegration. We have several complex business rules and integrated
with an AS400 so we pretty much take over all processnig control and let
BizTalk just 'pass' the message to us.

I use the ReleaseCOMObject is most of my Windows app, but not sure how to
control the DLLHOST from my DLL.

-r

"Christof" <bts2004communityfeedback (at) hotmail (dot) com> wrote in
message news:uLO8S3XIEHA.828@TK2MSFTNGP10.phx.gbl...
> If you use interop, make sure you call the Marshaller.ReleaseCOMObject.
> (Expecially true when using MSXML4 for some reason.)
>
>
> "Rich Wallace" <rich.wallace@minusthecannedmeat.jfsheadotcom> wrote in
> message news:OylYVQXIEHA.3040@TK2MSFTNGP09.phx.gbl...
memory[color=darkred]
> Schedule
> mange
> from
>
>



Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com