RE: debug during partitioning

Question

From personal experience you probably have some type of circularreferencing between objects during the Init() method processing. I've
run across this when the Init() method of a containing object
instantiates the contained objects and the contained objects have a
reference to the containing object. These classes begin a tight circle
of instantiating each other's objects until memory is exhausted.
Offhand I can't remember which, but running from the running man or the
debugger will eventually give you the out of memory message along with
responsible class.
Lee S. Fields
Advanced Fiber Systems, E. I. DuPont
[email protected]
-----Original Message-----
From: [email protected] [SMTP:[email protected]]
Sent: Monday, November 02, 1998 2:16 PM
To: [email protected]
Subject: debug during partitioning
I need a way to see what Forte is doing when it is returning my
application
to the client during a distributed run. What is happening is after
all the
server partitions start I get the message returning windows partition
to
the client. My client then runs out of memory. I have allocated 80MG
of
memory on the client and my app. only has 2 windows so I assume there
is
something else that I have partitioned poorly.
My question is how can I figure out what Forte is doing when it runs
out of
memory so I have a place to start looking ?
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive
<URL:http://pinehurst.sageit.com/listarchive/>-
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

Answer 1

Hi,
Use trace flags the following trace flag "trc:os:5:5"
for more details see the technotes
Thanks & Regards
Raju
(Pothuraju Katta)
[email protected]
Phone: [phone]
Fax: [phone]
-----Original Message-----
From: [email protected] [SMTP:[email protected]]
Sent: Monday, November 02, 1998 1:16 PM
To: [email protected]
Subject: debug during partitioning
I need a way to see what Forte is doing when it is returning my
application
to the client during a distributed run. What is happening is after
all the
server partitions start I get the message returning windows partition
to
the client. My client then runs out of memory. I have allocated 80MG
of
memory on the client and my app. only has 2 windows so I assume there
is
something else that I have partitioned poorly.
My question is how can I figure out what Forte is doing when it runs
out of
memory so I have a place to start looking ?
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive
<URL:http://pinehurst.sageit.com/listarchive/>-
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>