Can't Run program in Debug Mode
To:forte-users@Sagesoln.com
cc:
Subject: Can't Run program in Debug Mode
Has anyone else experienced this problem? We have written a non-express
program that uses the Express generated services project as a supplier
plan. However, when we try running this program in debug mode about 50%
(or more) of the time we abend while Forte is trying to partition the
application. Since we have many database classes in our Business Model we
are wondering if Forte is timing out during the partition phase or if the
server partition is running out of memory . The following error messages
are produced by Forte. Any suggestions?
=======================
Error messages on client:
=======================
SYSTEM ERROR: Unable to start the partition testacadprogoffer_CL0_Part1 on
any
of the nodes to which it has been assigned. See the remainder of the
error
stack for more information.
Class: qqsp_ResourceException
Error #: [1602, 593]
Detected at: qqcf_StandardConfig::LoadRemotePartition at 5
Last TOOL statement: method overview.StartApplication
Error Time: Tue Dec 02 12:56:01
Exception occurred (locally) on partition "Express_cl7_Client",
(partitionId = F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3,
taskId =
[F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3.226]) in application
"FTLaunch_cl0", pid 65 on node DWILBUR_NTWS in environment
CentralEnv.
SYSTEM ERROR: Unable to start partition testacadprogoffer_CL0_Part1 on node
admin2.
Class: qqsp_ErrorDescriptor
Error #: [1602, 592]
Detected at: qqcf_StandardConfig::LoadRemotePartition at 3
Error Time: Tue Dec 02 12:56:01
Exception occurred (locally) on partition "Express_cl7_Client",
(partitionId = F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3,
taskId =
[F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3.226]) in application
"FTLaunch_cl0", pid 65 on node DWILBUR_NTWS in environment
CentralEnv.
SYSTEM ERROR: Lost contact with remote server while trying to load
partition
testacadprogoffer_CL0_Part1. Check server log file for more information
about
the specific problem.
Class: qqsp_ResourceException
Error #: [1301, 102]
Detected at: qqem_IPartitionAgent::Startup at 5
Error Time: Tue Dec 02 12:56:01
Exception occurred (locally) on partition "Express_cl7_Client",
(partitionId = F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3,
taskId =
[F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3.226]) in application
"FTLaunch_cl0", pid 65 on node DWILBUR_NTWS in environment
CentralEnv.
INFORMATION: The connection to the partner was terminated by the
Communication
Manager for the reasons below.
Class: qqsp_DistAccessException
Detected at: qqdo_PartitionMgr::StopLocation at 1
Error Time: Tue Dec 02 12:56:00
Distributed method called: qqrt_ForteExecAgentProxy.LoadPartition!6
(object name Unnamed) from partition "Forte_Executor", (partitionId =
F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9, taskId =
[F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9.229]) in application
"FTLaunch_cl0", pid 65 on node DWILBUR_NTWS in environment CentralEnv
Exception occurred (locally) on partition "Express_cl7_Client",
(partitionId = F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3,
taskId =
[F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3.226]) in application
"FTLaunch_cl0", pid 65 on node DWILBUR_NTWS in environment
CentralEnv.
INFORMATION: Network partner closed connection. This usually means the
process at the other end of the wire failed. Please go look there and
find
out why.
Class: qqsp_DistAccessException
Detected at: qqcm_HoseFSM::ReceivedClose at 2
Error Time: Tue Dec 02 12:56:00
Exception occurred (locally) on partition "Express_cl7_Client",
(partitionId = F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3,
taskId =
[F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3.226]) in application
"FTLaunch_cl0", pid 65 on node DWILBUR_NTWS in environment
CentralEnv.
INFORMATION: Received close: Connection aborted (10053).
Class: qqsp_DistAccessException
Detected at: qqcm_HoseFSM::ReceivedClose at 1
Error Time: Tue Dec 02 12:56:00
Exception occurred (locally) on partition "Express_cl7_Client",
(partitionId = F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3,
taskId =
[F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3.226]) in application
"FTLaunch_cl0", pid 65 on node DWILBUR_NTWS in environment
CentralEnv.
=======================
Log messages on server:
=======================
Attached to manager for node admin2.
aud Tue Dec 2 09:34:36 : Loading partition testacadprogoffer_cl0_Part2
built on <unknown>.
Attached to manager for node admin2.
aud Tue Dec 2 09:41:58 : Shutting down partition as requested.
aud Tue Dec 2 09:41:59 : Unloaded partition testacadprogoffer_cl0_Part2.
aud Tue Dec 2 09:49:44 : Loading partition testacadprogoffer_cl0_Part2
built on <unknown>.
Attached to manager for node admin2.
aud Tue Dec 2 10:00:11 : Shutting down partition as requested.
aud Tue Dec 2 10:00:12 : Unloaded partition testacadprogoffer_cl0_Part2.
aud Tue Dec 2 10:18:34 : Loading partition testacadprogoffer_cl0_Part3
built on <unknown>.
Attached to manager for node admin2.
aud Tue Dec 2 10:27:00 : Shutting down partition as requested.
aud Tue Dec 2 10:27:00 : Unloaded partition testacadprogoffer_cl0_Part3.
aud Tue Dec 2 10:47:03 : Loading partition
EvaluateApplRequirementsBO_CL0_Part1 built on <unknown>.
Attached to manager for node admin2.
aud Tue Dec 2 11:09:26 : Shutting down partition due to failure of agent
owner's partition.
aud Tue Dec 2 11:09:26 : Shutting down partition as requested.
aud Tue Dec 2 11:09:26 : Unloaded partition
EvaluateApplRequirementsBO_CL0_Part1.
aud Tue Dec 2 12:36:14 : Loading partition testacadprogoffer_CL0_Part1
built on <unknown>.
Attached to manager for node admin2.
aud Tue Dec 2 12:45:17 : Shutting down partition as requested.
aud Tue Dec 2 12:45:17 : Unloaded partition testacadprogoffer_CL0_Part1.
FATAL ERROR: Out of Memory (reason = qqOS_MM_EX_OUT_OF_MEMORY)
FATAL ERROR: Out of Memory (reason = qqOS_MM_EX_OUT_OF_MEMORY)
Task 11: qqcm_HoseRecvServiceTask::Run: Caught unexpected exception
FATAL ERROR: ************* Out of Memory, requested (1K) available (0K)
Class: qqsp_ResourceException with ReasonCode: SP_ER_OUTOFMEMORY
Detected at: qqos_MemoryManager
Error Time: Tue Dec 2 12:49:01
Exception occurred (locally) on partition "Forte_Executor",
(partitionId = F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10f3, t
askId = [F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10f3.11]) in application
"Forte Runtime", pid 14020 on node admin2 in environ
ment CentralEnv.
FATAL ERROR: ************* Out of Memory, requested (1K) available (0K)
Class: qqsp_ResourceException with ReasonCode: SP_ER_OUTOFMEMORY
Detected at: qqos_MemoryManager
Error Time: Tue Dec 2 12:48:57
FATAL ERROR: Out of Memory (reason = qqOS_MM_EX_OUT_OF_MEMORY)
FATAL ERROR: Out of Memory (reason = qqOS_MM_EX_OUT_OF_MEMORY)
ERROR: TMgr.RunThread: task cm.Recv failed terminating.
Probably caused by a FATAL exception.
-
David Wilburemail: dwilbur@uwindsor.ca
University of Windsorphone: 519-253-3000 ext. 2779
Windsor, Ontario Canada
--
[7984 byte] By [
] at [2007-11-25 5:01:11]
Hi,
We have had the same problem in a non-express application
with a heavy server partition. In our case, the error was not
systematic, depending on the server workload at the time we
tried to partition and run.
The work-around we're using is to put the -fm flags (increasing the x
parameter to say 30000) in the 'server arguments' of your server
partition
properties in the partition workshop. Note that if your server is a Unix
platform,
you need to put double-quotes before and after the parenthesis in the -fm
syntax.
Hope this helps,
Vincent Figari
BTW, what Forte version are you using ?
On Tue, 2 Dec 1997 13:44:24 -0500 "David Wilbur"<dwilbur@uwindsor.ca>
writes:
>
>
>
>
>
>To:forte-users@Sagesoln.com
>cc:
>Subject: Can't Run program in Debug Mode
>
>
>
>Has anyone else experienced this problem? We have written a
>non-express
>program that uses the Express generated services project as a supplier
>plan. However, when we try running this program in debug mode about
>50%
>(or more) of the time we abend while Forte is trying to partition the
>application. Since we have many database classes in our Business
>Model we
>are wondering if Forte is timing out during the partition phase or if
>the
>server partition is running out of memory . The following error
>messages
>are produced by Forte. Any suggestions?
>
>
>=======================
>Error messages on client:
>=======================
>
>SYSTEM ERROR: Unable to start the partition
>testacadprogoffer_CL0_Part1 on
>any
> of the nodes to which it has been assigned. See the remainder of
>the
>error
> stack for more information.
>Class: qqsp_ResourceException
>Error #: [1602, 593]
>Detected at: qqcf_StandardConfig::LoadRemotePartition at 5
>Last TOOL statement: method overview.StartApplication
>Error Time: Tue Dec 02 12:56:01
>Exception occurred (locally) on partition "Express_cl7_Client",
>(partitionId = F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3,
>taskId =
>[F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3.226]) in
>application
>"FTLaunch_cl0", pid 65 on node DWILBUR_NTWS in environment
>CentralEnv.
>SYSTEM ERROR: Unable to start partition testacadprogoffer_CL0_Part1 on
>node
> admin2.
>Class: qqsp_ErrorDescriptor
>Error #: [1602, 592]
>Detected at: qqcf_StandardConfig::LoadRemotePartition at 3
>Error Time: Tue Dec 02 12:56:01
>Exception occurred (locally) on partition "Express_cl7_Client",
>(partitionId = F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3,
>taskId =
>[F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3.226]) in
>application
>"FTLaunch_cl0", pid 65 on node DWILBUR_NTWS in environment
>CentralEnv.
>SYSTEM ERROR: Lost contact with remote server while trying to load
>partition
> testacadprogoffer_CL0_Part1. Check server log file for more
>information
>about
> the specific problem.
>Class: qqsp_ResourceException
>Error #: [1301, 102]
>Detected at: qqem_IPartitionAgent::Startup at 5
>Error Time: Tue Dec 02 12:56:01
>Exception occurred (locally) on partition "Express_cl7_Client",
>(partitionId = F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3,
>taskId =
>[F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3.226]) in
>application
>"FTLaunch_cl0", pid 65 on node DWILBUR_NTWS in environment
>CentralEnv.
>INFORMATION: The connection to the partner was terminated by the
>Communication
> Manager for the reasons below.
>Class: qqsp_DistAccessException
>Detected at: qqdo_PartitionMgr::StopLocation at 1
>Error Time: Tue Dec 02 12:56:00
>Distributed method called:
>qqrt_ForteExecAgentProxy.LoadPartition!6
>(object name Unnamed) from partition "Forte_Executor",
>(partitionId =
>F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9, taskId =
>[F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9.229]) in
>application
>"FTLaunch_cl0", pid 65 on node DWILBUR_NTWS in environment
>CentralEnv
>Exception occurred (locally) on partition "Express_cl7_Client",
>(partitionId = F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3,
>taskId =
>[F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3.226]) in
>application
>"FTLaunch_cl0", pid 65 on node DWILBUR_NTWS in environment
>CentralEnv.
>INFORMATION: Network partner closed connection. This usually means
>the
> process at the other end of the wire failed. Please go look there
>and
>find
> out why.
>Class: qqsp_DistAccessException
>Detected at: qqcm_HoseFSM::ReceivedClose at 2
>Error Time: Tue Dec 02 12:56:00
>Exception occurred (locally) on partition "Express_cl7_Client",
>(partitionId = F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3,
>taskId =
>[F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3.226]) in
>application
>"FTLaunch_cl0", pid 65 on node DWILBUR_NTWS in environment
>CentralEnv.
>INFORMATION: Received close: Connection aborted (10053).
>Class: qqsp_DistAccessException
>Detected at: qqcm_HoseFSM::ReceivedClose at 1
>Error Time: Tue Dec 02 12:56:00
>Exception occurred (locally) on partition "Express_cl7_Client",
>(partitionId = F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3,
>taskId =
>[F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3.226]) in
>application
>"FTLaunch_cl0", pid 65 on node DWILBUR_NTWS in environment
>CentralEnv.
>
>
>=======================
>Log messages on server:
>=======================
>
>Attached to manager for node admin2.
>aud Tue Dec 2 09:34:36 : Loading partition
>testacadprogoffer_cl0_Part2
>built on <unknown>.
>Attached to manager for node admin2.
>aud Tue Dec 2 09:41:58 : Shutting down partition as requested.
>aud Tue Dec 2 09:41:59 : Unloaded partition
>testacadprogoffer_cl0_Part2.
>aud Tue Dec 2 09:49:44 : Loading partition
>testacadprogoffer_cl0_Part2
>built on <unknown>.
>Attached to manager for node admin2.
>aud Tue Dec 2 10:00:11 : Shutting down partition as requested.
>aud Tue Dec 2 10:00:12 : Unloaded partition
>testacadprogoffer_cl0_Part2.
>aud Tue Dec 2 10:18:34 : Loading partition
>testacadprogoffer_cl0_Part3
>built on <unknown>.
>Attached to manager for node admin2.
>aud Tue Dec 2 10:27:00 : Shutting down partition as requested.
>aud Tue Dec 2 10:27:00 : Unloaded partition
>testacadprogoffer_cl0_Part3.
>aud Tue Dec 2 10:47:03 : Loading partition
>EvaluateApplRequirementsBO_CL0_Part1 built on <unknown>.
>Attached to manager for node admin2.
>aud Tue Dec 2 11:09:26 : Shutting down partition due to failure of
>agent
>owner's partition.
>aud Tue Dec 2 11:09:26 : Shutting down partition as requested.
>aud Tue Dec 2 11:09:26 : Unloaded partition
>EvaluateApplRequirementsBO_CL0_Part1.
>aud Tue Dec 2 12:36:14 : Loading partition
>testacadprogoffer_CL0_Part1
>built on <unknown>.
>Attached to manager for node admin2.
>aud Tue Dec 2 12:45:17 : Shutting down partition as requested.
>aud Tue Dec 2 12:45:17 : Unloaded partition
>testacadprogoffer_CL0_Part1.
>
>FATAL ERROR: Out of Memory (reason = qqOS_MM_EX_OUT_OF_MEMORY)
>
>FATAL ERROR: Out of Memory (reason = qqOS_MM_EX_OUT_OF_MEMORY)
>Task 11: qqcm_HoseRecvServiceTask::Run: Caught unexpected exception
>FATAL ERROR: ************* Out of Memory, requested (1K) available
>(0K)
>Class: qqsp_ResourceException with ReasonCode: SP_ER_OUTOFMEMORY
>Detected at: qqos_MemoryManager
>Error Time: Tue Dec 2 12:49:01
>Exception occurred (locally) on partition "Forte_Executor",
>(partitionId = F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10f3, t
>askId = [F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10f3.11]) in
>application
>"Forte Runtime", pid 14020 on node admin2 in environ
>ment CentralEnv.
>
>FATAL ERROR: ************* Out of Memory, requested (1K) available
>(0K)
>Class: qqsp_ResourceException with ReasonCode:
>SP_ER_OUTOFMEMORY
>Detected at: qqos_MemoryManager
>Error Time: Tue Dec 2 12:48:57
>
>FATAL ERROR: Out of Memory (reason = qqOS_MM_EX_OUT_OF_MEMORY)
>
>FATAL ERROR: Out of Memory (reason = qqOS_MM_EX_OUT_OF_MEMORY)
>ERROR: TMgr.RunThread: task cm.Recv failed terminating.
>Probably caused by a FATAL exception.
>
>-
>David Wilburemail: dwilbur@uwindsor.ca
>University of Windsorphone: 519-253-3000 ext. 2779
>Windsor, Ontario Canada
>--
>
>
>
at 2007-6-29 9:20:26 >
We have experience out of memory problems while attempting to run in
debug mode. This can be componded if you don't compile your application
before attempting to run the debugger. The combination of compiling
your application when running the debugger can be very memory intensive,
especially with Express applications.
Kal Inman
Andersen Windows
> --Original Message--
> From: David Wilbur [SMTP:dwilbur@uwindsor.ca]
> Sent: Tuesday, December 02, 1997 12:44 PM
> To:kamranamin@yahoo.com
> Subject:Can't Run program in Debug Mode
>
>
>
>
>
>
> To:forte-users@Sagesoln.com
> cc:
> Subject: Can't Run program in Debug Mode
>
>
>
> Has anyone else experienced this problem? We have written a
> non-express
> program that uses the Express generated services project as a supplier
> plan. However, when we try running this program in debug mode about
> 50%
> (or more) of the time we abend while Forte is trying to partition the
> application. Since we have many database classes in our Business
> Model we
> are wondering if Forte is timing out during the partition phase or if
> the
> server partition is running out of memory . The following error
> messages
> are produced by Forte. Any suggestions?
>
>
> =======================
> Error messages on client:
> =======================
>
> SYSTEM ERROR: Unable to start the partition
> testacadprogoffer_CL0_Part1 on
> any
>of the nodes to which it has been assigned. See the remainder of
> the
> error
>stack for more information.
>Class: qqsp_ResourceException
>Error #: [1602, 593]
>Detected at: qqcf_StandardConfig::LoadRemotePartition at 5
>Last TOOL statement: method overview.StartApplication
>Error Time: Tue Dec 02 12:56:01
>Exception occurred (locally) on partition "Express_cl7_Client",
>(partitionId = F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3,
> taskId =
>[F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3.226]) in
> application
>"FTLaunch_cl0", pid 65 on node DWILBUR_NTWS in environment
> CentralEnv.
> SYSTEM ERROR: Unable to start partition testacadprogoffer_CL0_Part1 on
> node
>admin2.
>Class: qqsp_ErrorDescriptor
>Error #: [1602, 592]
>Detected at: qqcf_StandardConfig::LoadRemotePartition at 3
>Error Time: Tue Dec 02 12:56:01
>Exception occurred (locally) on partition "Express_cl7_Client",
>(partitionId = F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3,
> taskId =
>[F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3.226]) in
> application
>"FTLaunch_cl0", pid 65 on node DWILBUR_NTWS in environment
> CentralEnv.
> SYSTEM ERROR: Lost contact with remote server while trying to load
> partition
>testacadprogoffer_CL0_Part1. Check server log file for more
> information
> about
>the specific problem.
>Class: qqsp_ResourceException
>Error #: [1301, 102]
>Detected at: qqem_IPartitionAgent::Startup at 5
>Error Time: Tue Dec 02 12:56:01
>Exception occurred (locally) on partition "Express_cl7_Client",
>(partitionId = F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3,
> taskId =
>[F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3.226]) in
> application
>"FTLaunch_cl0", pid 65 on node DWILBUR_NTWS in environment
> CentralEnv.
> INFORMATION: The connection to the partner was terminated by the
> Communication
>Manager for the reasons below.
>Class: qqsp_DistAccessException
>Detected at: qqdo_PartitionMgr::StopLocation at 1
>Error Time: Tue Dec 02 12:56:00
>Distributed method called:
> qqrt_ForteExecAgentProxy.LoadPartition!6
>(object name Unnamed) from partition "Forte_Executor",
> (partitionId =
>F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9, taskId =
>[F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9.229]) in
> application
>"FTLaunch_cl0", pid 65 on node DWILBUR_NTWS in environment
> CentralEnv
>Exception occurred (locally) on partition "Express_cl7_Client",
>(partitionId = F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3,
> taskId =
>[F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3.226]) in
> application
>"FTLaunch_cl0", pid 65 on node DWILBUR_NTWS in environment
> CentralEnv.
> INFORMATION: Network partner closed connection. This usually means
> the
>process at the other end of the wire failed. Please go look there
> and
> find
>out why.
>Class: qqsp_DistAccessException
>Detected at: qqcm_HoseFSM::ReceivedClose at 2
>Error Time: Tue Dec 02 12:56:00
>Exception occurred (locally) on partition "Express_cl7_Client",
>(partitionId = F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3,
> taskId =
>[F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3.226]) in
> application
>"FTLaunch_cl0", pid 65 on node DWILBUR_NTWS in environment
> CentralEnv.
> INFORMATION: Received close: Connection aborted (10053).
>Class: qqsp_DistAccessException
>Detected at: qqcm_HoseFSM::ReceivedClose at 1
>Error Time: Tue Dec 02 12:56:00
>Exception occurred (locally) on partition "Express_cl7_Client",
>(partitionId = F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3,
> taskId =
>[F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3.226]) in
> application
>"FTLaunch_cl0", pid 65 on node DWILBUR_NTWS in environment
> CentralEnv.
>
>
> =======================
> Log messages on server:
> =======================
>
> Attached to manager for node admin2.
> aud Tue Dec 2 09:34:36 : Loading partition
> testacadprogoffer_cl0_Part2
> built on <unknown>.
> Attached to manager for node admin2.
> aud Tue Dec 2 09:41:58 : Shutting down partition as requested.
> aud Tue Dec 2 09:41:59 : Unloaded partition
> testacadprogoffer_cl0_Part2.
> aud Tue Dec 2 09:49:44 : Loading partition
> testacadprogoffer_cl0_Part2
> built on <unknown>.
> Attached to manager for node admin2.
> aud Tue Dec 2 10:00:11 : Shutting down partition as requested.
> aud Tue Dec 2 10:00:12 : Unloaded partition
> testacadprogoffer_cl0_Part2.
> aud Tue Dec 2 10:18:34 : Loading partition
> testacadprogoffer_cl0_Part3
> built on <unknown>.
> Attached to manager for node admin2.
> aud Tue Dec 2 10:27:00 : Shutting down partition as requested.
> aud Tue Dec 2 10:27:00 : Unloaded partition
> testacadprogoffer_cl0_Part3.
> aud Tue Dec 2 10:47:03 : Loading partition
> EvaluateApplRequirementsBO_CL0_Part1 built on <unknown>.
> Attached to manager for node admin2.
> aud Tue Dec 2 11:09:26 : Shutting down partition due to failure of
> agent
> owner's partition.
> aud Tue Dec 2 11:09:26 : Shutting down partition as requested.
> aud Tue Dec 2 11:09:26 : Unloaded partition
> EvaluateApplRequirementsBO_CL0_Part1.
> aud Tue Dec 2 12:36:14 : Loading partition
> testacadprogoffer_CL0_Part1
> built on <unknown>.
> Attached to manager for node admin2.
> aud Tue Dec 2 12:45:17 : Shutting down partition as requested.
> aud Tue Dec 2 12:45:17 : Unloaded partition
> testacadprogoffer_CL0_Part1.
>
> FATAL ERROR: Out of Memory (reason = qqOS_MM_EX_OUT_OF_MEMORY)
>
> FATAL ERROR: Out of Memory (reason = qqOS_MM_EX_OUT_OF_MEMORY)
> Task 11: qqcm_HoseRecvServiceTask::Run: Caught unexpected exception
> FATAL ERROR: ************* Out of Memory, requested (1K) available
> (0K)
>Class: qqsp_ResourceException with ReasonCode: SP_ER_OUTOFMEMORY
>Detected at: qqos_MemoryManager
>Error Time: Tue Dec 2 12:49:01
>Exception occurred (locally) on partition "Forte_Executor",
> (partitionId = F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10f3, t
> askId = [F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10f3.11]) in
> application
> "Forte Runtime", pid 14020 on node admin2 in environ
> ment CentralEnv.
>
>FATAL ERROR: ************* Out of Memory, requested (1K) available
> (0K)
> Class: qqsp_ResourceException with ReasonCode:
> SP_ER_OUTOFMEMORY
> Detected at: qqos_MemoryManager
> Error Time: Tue Dec 2 12:48:57
>
> FATAL ERROR: Out of Memory (reason = qqOS_MM_EX_OUT_OF_MEMORY)
>
> FATAL ERROR: Out of Memory (reason = qqOS_MM_EX_OUT_OF_MEMORY)
> ERROR: TMgr.RunThread: task cm.Recv failed terminating.
> Probably caused by a FATAL exception.
>
> -
> David Wilburemail: dwilbur@uwindsor.ca
> University of Windsorphone: 519-253-3000 ext. 2779
> Windsor, Ontario Canada
> --
>
at 2007-6-29 9:20:26 >
