Re: Huge problem with COM+ performace? PART TWO

From: Adam Boczek <adam.boczek_at_NO_SPAM_gft-solutions.de>
Date: Thu, 1 Nov 2001 11:05:38 +0100
Message-ID: <1004609137.187138@tux2.ham.acs-gmbh.de>

Thanx for hint but I have tried all possibilities (BTW CreateInstance has to be used with "old" MTS).

Greets,
Adam

---

Adam Boczek
IT Consultant
GFT Solutions GmbH
adam.boczek_at_gft-solutions.de

---

"Niall Litchfield" <n-litchfield_at_audit-commission.gov.uk> schrieb im Newsbeitrag news:3be11c89$0$8512$ed9e5944_at_reading.news.pipex.net...
> "Adam Boczek" <adam.boczek_at_NO_SPAM_gft-solutions.de> wrote in message
> news:1004553339.429437_at_tux2.ham.acs-gmbh.de...
> > First of all I'd like to thanx all of you for answers!
> <snip>
> > Suddenly I've found in log event, that my second client can't initialize
> > com+ object (stops when I call "set a = new MyDll.Function"). When the
> first
> > client realises or creates new object than some resouces are free and
> second
> > client goes on, but stops when it once again needs new object. So it
looks
> > like problems by resource pooling in com+.
>
> Try replacing
>
> set a = New MYDLL.....
>
> with
>
> set a = CreateObject("mydll class string")
>
> I believe there was also a reference to a call to createinstance(something
> or other) but as you can tell I'm ot familiar with that syntax.
>
>
>
> --
> Niall Litchfield
> Oracle DBA
> Audit Commission Uk
>
>
>
Received on Thu Nov 01 2001 - 04:05:38 CST