Can't Run program in Debug Mode

To: [email protected]
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 Wilbur email: [email protected]
University of Windsor phone: 519-253-3000 ext. 2779
Windsor, Ontario Canada
-----------------------------------------------

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"<[email protected]>
writes:
>
>
>
>
>
To: [email protected]
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 Wilbur email: [email protected]
University of Windsor phone: 519-253-3000 ext. 2779
Windsor, Ontario Canada

Similar Messages

How to run labview program in debugging mode in windows 95 version

Respected all,
I am facing probelm while running probe.vi.
I received this command "connection to acquisition board was not found" when i run labview program.
I am using labview 5.1, fieldpoint FP 1000, NI-DAQ 6.5, Field point explorer version 1.6, Measurement and Automation Explorer 1.0.1.
I would kindly request you please help me how to run my program probe.vi in debugging mode in windows 95 version, so that i can locate where error occurs.
Thanking You
Yours faithfully
M.Vijay

Respected Norbert,
Thank you very much to for your help.
Norbert : Possible reasons are e.g. wrong IDs for measurement devices. If the error is connect to the FieldPoint, it is possible that it isn't configured correctly.
I am using Field point explorer 1.6, The Field point instrument FP 1000 and RS-232 port is using. It is confirmed that the field point instrument is working properly by LED light indication test.
Norbert: It sound like you are using DAQ devices (like PCI MIO 6952E) in the application. Are you sure that you select the correct device ID for this?
I am asking you to know, If i using Labview and Fieldpoint instrument FP 1000 to monitor my parameter interms of All, Channel 0, Channel 1, Channel 2, Channel 3, Channel 4, Channel 5, Channel 6, Channel 7 for my measurement.
But now i need to solve the command connection to acquisition board was not found, The expert say this command is due to there was no AT-AO-10 Analog Output board was present in CPU.
I do not find AT-AO-10 Analog Output board in my CPU, Previously the instrument was worked perfectly by other person who assembled everthing to measure temperature.
The only aswer know send by previous person is if my task does not imply the use of a DAQ you probably have to locate where the DAQ driver is called and exclude it from the program. try to run the program in debugging mode so that you can locate where the error occurs.
I do not know how to proceed his instruction. So i would kindly request you to please help me to solve my probelm.
I also removed AT-AO-10 software from device manager >> Data Acquisition system >> AT-AO-10 just now.
I also find GPIB version 1.30, when i remove in add or remove program, it say that Error removing the GPIB.
I am eagerly waiting for your help.
Thanking You
Yours faithfully
M.vijay

Program running fine in Debug mode but failing in direct execution

Hi All,
I am facing a peculiar problem, I have created a report that create STO then Delivery and then Shipment one after one. I have used BAPI to do so. If STO creation is successful then Create Delivery and if delivery creation is also successfull then create Shipment.
When I run this program by pressing execute button it is only creating STO and coming out ,but if I run it in Debug mode I get all the three( STO, Delivey,Shipment). Since it run fine in debug so I can't found where the problem is.
Can any one help???
Regards
Hemant

Hi guys,
A learning for me .... how important WAIt parmeter is in commit work .. Initially i have not set WAIT paramater in commit BAPI to X due to this further processing.. Delivery and Shipment creation was failing in direct execution ... as after STO creation I was reding EKPO and that was failing in direct execution , but in backgroung everything was ok.
Thanks for your time.
Cheers
Hemant

Project runs Ok in debug mode but not in release mode

I have an application developed with VC++ 6.0 and measurement studio. The application controls SCXI-1161/1166 relay boards to connect the UUT. The application runs ok in debug mode, but in release mode the application can't drive the relay boards. I have tried to change optimizations mode, it didn't work. Who can tell me how to solve the problem? Thanks!

It sounds like you have an older version of our SWITCH driver which relies on our DAQ driver. I would recommend uninstalling the Traditional DAQ, DAQmx, and SWITCH drivers and then installing the newest version. At this point you have 2 options:
1) You can download Traditional DAQ 7.4, DAQmx 7.4, and NI-SWITCH 2.4 drivers bundled together here: ftp://ftp.ni.com/support/daq/pc/ni-daq/7.4/
2) You can install the latest version: NI-DAQmx 7.5 here: http://digital.ni.com/softlib.nsf/websearch/CF7ECCEA4C4CC7DE86257038004D88AE?opendocument&node=13206... This has support for all of our USB DAQ devices (if you're not using them then you may not want to worry about installing this now) and then install Traditional DAQ 7.4 here: http://digital.ni.com/softlib.nsf/websearch/C36A54ADDA3DC33D86257038004E55E6?opendocument&node=13206... and NI-SWITCH 2.4 here: http://digital.ni.com/softlib.nsf/websearch/9D6B8C7FD41BF3D08625702E0072E294?opendocument&node=13206...
This should solve your problem.

Eroor in eclipse when i have run TOMCAT in debuge mode web service debuging

hello all,
i have a serious problem with debug my web service. I set local variable in eclipse (-Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=8000). And now if i run TOMCAT in normal mode all worked fine and i run remote java application fine, but if i run TOMCAT in debug mode, eclipse in console return error:
"Error occurred during initialization of VM
agent library failed to init: jdwp
ERROR: Cannot load this JVM TI agent twice, check your java command line for duplicate jdwp options."
If anyone have this problem please tell me how to resolved it.
Thank for help.

Eclipse is kind of a competing product so this is not the best place to ask the question. With that most will be nice enough to lend a hand. I suggest ensuring that all other instances of tomcat are stopped then try again. In the Debug perspective ensure there are no servers running with the same name as the one you are attempting to use. If all else fails ensure there are no tomcat process running if they are kill them. Finally, if you cant get it to work reboot. If still no good the Eclipse might be a better place to go.

How to run labview in debug mode

Two questions:
1. how to run labview in debug mode
2. how to save default text values in labview

Hi,
consider i have streaming bits of data as input who length varies each time. I need to select 11 bits at a time and apply (15,11) hamming coding for the inputs till the input is stopped.
I have designed the hamming encoding and decoding block. I need a methodology to select 11 bits at a time from the input and provide to the hamming encoder.
eg: if input is 1100 bits, output must be 1500 bits.
I have uploaded the encoder and the decoder part. Please suggest me the design to read the input and append the output.
Attachments:
project_HammingEncode.vi ‏19 KB
project_HammingDecode.vi ‏22 KB

Mountain Lion broke vectordesigner 1.7.0. Can I run it in compatibility mode to Lion?

Hi,
if anyone could help? Mountain Lion broke vectordesigner 1.7.0. Can I run it in compatibility mode to Lion?
I can not update to version 1.7.3 because it has been removed from the app store.
Regards
Steffan

There isn't a "compatibility" mode.
According to Roaring Apps compatibility table, neither version works with Mountaion Lion.
http://roaringapps.com/apps:table/tags/_v/index_tags/_v

Running APPS in Debug Mode

Hi all,
I would like to know how to run APPS in Debug Mode. I know the steps to enable debug mode at apps tier server level as below...
Log into the apps tier server as apps tier manager.
Edit $APACHE_TOP/Apache/conf/httpd.conf
LogLevel debug
Edit $APACHE_TOP/Jserv/etc/jserv.conf
ApJServLogLevel debug
Edit $APACHE_TOPJserv/etc/jserv.properties
log=true
wrapper.bin.parameters=-DAFLOG_ENABLED=TRUE
wrapper.bin.parameters=-DAFLOG_LEVEL=UNEXPECTED
wrapper.bin.parameters=-DAFLOG_MODULE=%
wrapper.bin.parameters=-DAFLOG_FILENAME=$APACHE_TOP/Apache/logs/aferror.log
Edit $APACHE_TOP/Jserv/etc/ssp_init.txt
DebugLevel=5
DebugSwitch=ON
Bounce the Apache Services for changes to take effect.
Now my question is, I want to know how to debug APPS in freont end. i.e.., I want to do it in APPS screens, if I do it at the apps tier server level, it'll be for all. But I want to do it for a single user (Just like running GUI tools such as VB,D2k in DEBUG mode).
Regards
-Mahesh

Hi Sharon,
Thanx for the reply.
Actually, I don't want to debug using any profile values. As I pointed out, if we set the profile value debug mode is enabled for all the users using that particular module. But I want to do it for a single user, who wants to run in Debug Mode. Any more updates on this?
Regards
Mahesh

I keep getting message "This page requires a plugin that can only run in 32 bit mode" what does this mean and how can I fix it?

I keep getting message "This page requires a plugin that can only run in 32 bit mode" what does this mean and how can I fix it? It seems to come up randomly, but I'm fairly ignorant.

Previous versions of Firefox were only 32 bit, Firefox 4 for the Mac contains 32 and 64 bit versions. If you want to always start Firefox in 32 bit mode, open up Finder and go to the Applications folder. Control-click the Firefox app and click "Get Info", then select the "Open in 32-bit mode" option.

Can you run programs from time capsule? IE can I run microsoft office from it?

can you run programs from time capsule? IE can I run microsoft office from it?

Yes, probably can.. but it won't be fast. You are better storing programs locally and data remotely.

Error message says "This page requires a plugin that can only run in 32-bit mode"

When I try to write an email from my BT site I get the following message
"This page requires a plugin that can only run in 32-bit mode"
Then there's a link to restart the page in 32-bit mode. However, it resets to whole page, drags things back out the trash.
I have only had this problem since updating to the latest Firefox

Previous versions of Firefox were only 32 bit, Firefox 4 for the Mac contains 32 and 64 bit versions. If you want to always start Firefox in 32 bit mode, open up Finder and go to the Applications folder. Control-click the Firefox app and click "Get Info", then select the "Open in 32-bit mode" option.

Why can't I run in non-debug mode???

I recently copied a JSC project into another project using the "Save Project As" option when right clicking on the project name.
The new project appeared to copy fine and I was able to bild and run the project normally.
Somewhere along the line, I did something that changed something to where I can no longer run the project in 'non-debug' mode by using either the 'Run Main Project Ctrl+F5' under the 'Run' menu or by clicking the Right Green 'Run" triangle on the main menu.
The project builds successfully, but never runs in the browser.
I have tried stopping the server and everything else I can think of, but nothing works.
I can select 'Debug Main Project F5' from the 'Run' menu and it will build and start in the browser.
Other projects, including the source for this one, run fine in 'nion-debug' mode, but not this one.
How can I fix this??
I have run into instances where I get a message that says the build.xml file was altered externallt and was rebuilt. Is there any way to force a remake of the build.xml file using "Standard" defaults?
Thanks

The reason for copying the project was in order to create another very similar product that required only minor modifications at this time.
I got around the problem by doing another project copy and then using Beyond Compare to update the new copy with modifications I made to the original copy.
That worked.
My basic question was what would cause the problem that would create the situation where you could run in debug mode, but not non-debug mode.
This happened after the original copy (that worked fine) and after I had done most of the required modifications.
My thought was that there was some file or parameter that I could change rather than redoing the process.
Apparently not......................

Stopping a program in debug mode

Hi all,
i have am having a intermitent issue with a program. first let me give you the issue and then the specs.
This is an inconsistant program lockup. when the program runs in an, .exe format it runs fine for an hour to a couple of days and then goes to a white screen and freezes. the program is basically just continiously reading a DAQ card and comparing readings to set values.
if i have the program running in Debug mode thru CVI and it freezes, CVI sees it as running (in top left hand corner of CVI interface), if i push the stop button (break execution) the break execution dims but the program never stops and the Running indication is still active.
question--- is there another way to stop the program while it is in this frozen state to see where the issue is hanging up. like a hard stop command ????
I can only stop the program by using task manager and ending CVI there. which does me no good in finding the freezing point.
CVI 2012 sp1
with a PCI 6071E DAQ

There isn't an easy way to debug this kind of events.
The behaviour you are seeing (stop button dimmed after click but program that soesn't stop) normally happens when the program is stuck in a operation waiting for it to finish before breaking into the IDE. It may be a popup message waiting for user input, a I/O operation with a long or infinite timeout...
To deal with such a kind of thing you can for example write operations to a log file -one line before each critical call and one after that- so that you can at least see where it hanged. Alternatively you can use DebugPrintf to write messages to the debug output window: if in the IDE you have this window listed in Windows menu, if an .exe you can use utilities like DebugView to receive those messages. Another alternative can be to use Remote Debugging.
However, this is only a list of possible instruments and techniques: solving these problems usually ends up in a boring task of trial and error to narrow down to the critical situation and trying to overcome it.
Proud to use LW/CVI from 3.1 on.
My contributions to the Developer Zone Community
If I have helped you, why not giving me a kudos?

Run form in debug mode with windows vista

hi guys
plz help me
i'm using oracle forms 10g r2 on windows vista home primume and everything is ok but
when i need to run any form in debug mode i get the following
the jvm 1.4 give me jvm is aborting after that
the oc4j give me the following error frm-92101 there was a failure in the form server during start up
thanks

Hi Manoj,
You can do it directly from felix console. just go to http://<host>:<port>/system/console/slinglog there you will see all log files. under first table "Log Level" you will see all the log files and besides to that you will have configuration option, just go there and set log level for each of log files and save it.
Let me know if you need more information.
Thanks,
Pawan

Code runs fine in debug mode but hangs when compiled in release mode

I am struggling with the following problem. I have code which runs fine when it is executed in debug mode. However, when I compile it in release mode and run the executable, the code freezes and does not work. The code acquires images from a Hamamatsu camera. In the debug mode I am able to continuously acquire images. However, in the release version, the code hangs after acquiring the first image.
I am using LabWindows/CVI version 7.
I would greatly appreciate if I can get any help/suggestions in resolving this problem?
Thanks!
Regards,
Sripad
Solved!
Go to Solution.

Sripad:
If you search this forum for "debug release crash" or "release version crash" or similar phrases, you'll find that this is a pretty common question. Look through the other posts you find here to see if anything is applicable to you.
The debug version does some things like padding variables so you can sometimes overrun your declared variable space without overwriting the next variable. In the release, the variables are packed, so if you overrun one, you are overwriting another. Just one possible difference.
You can do some things in your release code to see where things get lost, like (temporarily using printf statements after multiple statements at the start and end of your loop to try to identify that failing line of code.
Look through other threads to find other ideas.

Can't Run program in Debug Mode

Similar Messages

Maybe you are looking for