MTS gives out of memory error

[bengeri]

Hi Friends,
We are developing a site with asp.
The configuration is as follows.
* win NT 4.0 sp 6a (asp 2.0, mts 2.0)
* sql server 7.0
* exchange5.5
* com developed in VB 6.0 and registered in mts

We are facing problem when there are simultaneous hits to
the site. We get either out of memory or server got
disconnected from the clients or some wierd error.
But at the server the mts always throws these two errors
in the event log whenever such a thing happens...in this
order.

1)
The run-time environment has detected an inconsistency in
its internal state and has terminated the process. Please
contact Microsoft Product Support Services to report this
error. Internal Check Failure on condition: m_lcBinds ==
0 (Package: BIComponents) (Microsoft Transaction
Server Internals Information: File:
i:\viper\src\runtime\mtxex\activity.cpp, Line: 287)

2)
Failed on creation from object context: CreateInstance
(ProgId: BIClasses.DBAccess) (CLSID: {EB6B72E4-D265-11D4-
B02B-00D0B76A10CD}) (Interface: IUnknown) (IID: {00000000-
0000-0000-C000-000000000046}) (Microsoft Transaction
Server Internals Information: File:
i:\viper\src\runtime\context\ccontext.cpp, Line: 1363)

This happens repeatedly..We searched for these errors and
found no clue as to what to do. We found in msdn that we
should set retain in memory and unattended execution for
vb dlls registered in mts.Even after doing there has not
been any improvement.

We thought this must be a problem of not having released
the objects. We changed the asp code to release all the
objects that we had created. Even after this the errors
are continuing.

And one interesting point is that the no. of concurrent
hits are not mere..merely 5-10.

Desperately need help.
Thanks and Regards,
Praveen

 

[volkoff]

1. Sometimes, when MTS trying to shutdown some package (internally, after "Minutes until idle ..." expired), it do it incorrectly. This way, I suggest you write small procedure, that creates all required objects, and executes before you do not need restart your server.
2. MTS make incorrect calls between packages on same computer(it is problem with marshalling, I suppose). So, as your ASP runs inside MTS package, try to move your classes on another comp.

 

[bengeri]

Thanx volkoff for the reply..
But i didn't get ur first point..
We have tested and found that its not because of the components getting shut down after particular amount of idle time...
The error is very random i.e. u can't predict it..but probability is high when u make simultaneous hits to the same asp.
I had even posted this question in msdn newsgroups but nobody replied to it.
We have even tried to put the components on different machine...but still the same problem...
That shows that either there is some problem with the way we have created and used objects in our components, or there is some problem with the mts that we are using.
Thanks and Regards,
Praveen

 

[chiph]

Praveen -

It sounds like you might be sharing some data between proceses (i.e. race-condition). Check your publicly-visible variables.

Chip H.

 

[axwl]

I face the same problem here. We have to do the load balancing by using extra 2 server.
Server1 - MTS
Server2 - IIS and Exhange
Server3 - SQL
Do not combined Exhange and DB together - used lots of resources.
Where are your DHCP located?
Other tips that worth to try :
- increase the DTC log files - it's realy helps on concurrentcy issues
- set you transaction time out of MTS to 3600 seconds and let the idle time shutdown of component package to default 3 minutes
- increase the virtual memory
- run the performance monitor monitor the processor time and page-faults - do estimation on the memory use by each and every component