Running AMIE in debug mode

How is it possible to activate debug mode for AMIE (Asset Management Integration Engine) ?

davidcacioli,
It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.
Has your problem been resolved? If not, you might try one of the following options:
- Visit http://support.novell.com and search the knowledgebase and/or check all
the other self support options and support programs available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.novell.com)
Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.novell.com/faq.php
If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.
Good luck!
Your Novell Product Support Forums Team
http://forums.novell.com/

Similar Messages

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

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

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

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

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.

Running Forms in Debug Mode (appletviewer / J-Initiater)

Hi All,
I have a sitiuation where i would like to run a form with debug_messages='YES'. The form is compiled under Forms 4.5 16 bit Windows 95. It is run with J-Initiater under a NCA enviroment. Is there a command parameter to run the fmx in debug mode, probably as a applet parameter or something.
Thanks,
Easo

Attaching to a Form running outside the builder
The advantage of attaching the debugger to a Form that runs outside of the Builder is that the Form can be running on a different machine other than the one debugging it. The configuration gives an end user the opportunity to run the Form and encounter errors while the developer debugs interactively with the user.
To start debugging a Form that runs outside the Builder, the Form must be invoked with the parameter Debug=yes passed in the URL. This parameter will invoke a dialog that displays the host name and port number.
In the Forms Builder, open the FMB for the running Form, and select Debug | Attach Debug. You'll need to supply the host name and port number to start debugging the running Form.

Running applications in debug mode in JDeveloper

Hi All,
I have created a simple spring portlet and have consumed it on a webcenter application. The portlet throws an exception. Now I want to run my portlet in debug mode.
Both webcenter application and portlet producer are running on the jdeveloper integrated server.
Can any one help me out mentioning steps to run the portlet and the portal app in debug mode.

Some info can be found in this thread in JDev forum: JDeveloper remote debugging OC4J
However, it is based on 10g and OC4J. Still, I believe, the overall concept can be used.

Running Form in Debug Mode: How? (Appletviewer/J initiater)

Hi All,
I have a sitiuation where i would like to run a form with debug_messages='YES'. The form is compiled under Forms 4.5 16 bit Windows 95. It is run with J-Initiater under a NCA enviroment. Is there a command parameter to run the fmx in debug mode, probably as a applet parameter or something.
Thanks,
Easo

You can also check Francois Degrelle excellent answer to the same question:
Running a form in debug mode

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......................

How do I run CRX in debug mode with CQ5 , CRX version is 1.0.1

I tried below commands But Attached Debug option under Debug menu option is still disabled.
Option 1 :
C:\author>java -debug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_sock
et,server=y,suspend=n,address=30303 -jar cq-author-4502.jar
Listening for transport dt_socket at address: 30303
Loading quickstart properties: default
Loading quickstart properties: instance
Low-memory action set to fork
Using 64bit VM settings, min.heap=1024MB, min permgen=256MB, default fork argume
nts=[-Xmx1024m, -XX:MaxPermSize=256m]
The JVM reports a heap size of 1781 MB, meets our expectation of 1024 MB +/- 20
**** WARNING: insufficent PermGen memory ***************************************
The JVM MBean:PS Perm Gen reports 82 MB but we recommend at least 256 MB +/- 20
Use your JVM's PermGen size option (like -XX:MaxPermSize=256M) to set that size.
Will fork a JVM to get enough memory.
Available memory below specified limits and low-memory action set to fork, will
fork to get enough memory
Preparing to fork JVM, OS name=Windows 7, isWindows=true
Forking JVM: [C:\Program Files\Java\jre6\bin\java.exe, -Xmx1024m, -XX:MaxPermSiz
e=256m, -jar, C:/author/cq-author-4502.jar, -nofork, -pt, CHILD]
Loading quickstart properties: default
Loading quickstart properties: instance
Low-memory action set to fork
Using 64bit VM settings, min.heap=1024MB, min permgen=256MB, default fork argume
nts=[-Xmx1024m, -XX:MaxPermSize=256m]
**** WARNING: insufficent heap memory ******************************************
The JVM reports 910 MB but we recommend at least 1024 MB +/- 20
Use your JVM's heap size option (like -Xmx1024M) to set that size.
Will fork a JVM to get enough memory.
The JVM MBean:PS Perm Gen reports a maximum size of 256 MB, meets our expectatio
n of 256 MB +/- 20
Available memory below specified limits and low-memory action set to fork, will
fork to get enough memory
Not forking JVM as -nofork option is set
Setting properties from filename 'C:/author/cq-author-4502.jar'
Property '-quickstart.server.port' set to '4502' from filename cq-author-4502.ja
r
Property '-r' set to 'author' from filename cq-author-4502.jar
Property '-r' is already set (author), ignoring new value (author) derived from
filename
System property 'sling.run.modes' set to 'author' by -r option
Verbose option not active, closing stdin and redirecting stdout and stderr
Redirecting stdout to C:\author\.\crx-quickstart\logs\stdout.log
Redirecting stderr to C:\author\.\crx-quickstart\logs\stderr.log
Press CTRL-C to shutdown the Quickstart server...
Shutdown
MAIN process: shutdown hook
MAIN process: Exception in shutdown hook: java.io.IOException: The pipe is being
closed
MAIN process: Wrote shutdown string to child process, waiting for it to exit (ma
x 5000 msec)
Child process did not exit? Destroying it now.
MAIN process: Child process exited.
MAIN process: exiting
Forked JVM process exited with exit code 1
Main JVM process exiting
OPtion 2:
C:\author>java -Xmx512m -Xdebug -Xrunjdwp:transport=dt_socket,server=y,address=3
0303,suspend=n -jar cq-author-4502.jar
Listening for transport dt_socket at address: 30303
Loading quickstart properties: default
Loading quickstart properties: instance
Low-memory action set to fork
Using 64bit VM settings, min.heap=1024MB, min permgen=256MB, default fork argume
nts=[-Xmx1024m, -XX:MaxPermSize=256m]
**** WARNING: insufficent heap memory ******************************************
The JVM reports 455 MB but we recommend at least 1024 MB +/- 20
Use your JVM's heap size option (like -Xmx1024M) to set that size.
Will fork a JVM to get enough memory.
**** WARNING: insufficent PermGen memory ***************************************
The JVM MBean:PS Perm Gen reports 82 MB but we recommend at least 256 MB +/- 20
Use your JVM's PermGen size option (like -XX:MaxPermSize=256M) to set that size.
Will fork a JVM to get enough memory.
Available memory below specified limits and low-memory action set to fork, will
fork to get enough memory
Preparing to fork JVM, OS name=Windows 7, isWindows=true
Forking JVM: [C:\Program Files\Java\jre6\bin\java.exe, -Xmx1024m, -XX:MaxPermSiz
e=256m, -jar, C:/author/cq-author-4502.jar, -nofork, -pt, CHILD]
Loading quickstart properties: default
Loading quickstart properties: instance
Low-memory action set to fork
Using 64bit VM settings, min.heap=1024MB, min permgen=256MB, default fork argume
nts=[-Xmx1024m, -XX:MaxPermSize=256m]
**** WARNING: insufficent heap memory ******************************************
The JVM reports 910 MB but we recommend at least 1024 MB +/- 20
Use your JVM's heap size option (like -Xmx1024M) to set that size.
Will fork a JVM to get enough memory.
The JVM MBean:PS Perm Gen reports a maximum size of 256 MB, meets our expectatio
n of 256 MB +/- 20
Available memory below specified limits and low-memory action set to fork, will
fork to get enough memory
Not forking JVM as -nofork option is set
Setting properties from filename 'C:/author/cq-author-4502.jar'
Property '-quickstart.server.port' set to '4502' from filename cq-author-4502.ja
r
Property '-r' set to 'author' from filename cq-author-4502.jar
Property '-r' is already set (author), ignoring new value (author) derived from
filename
System property 'sling.run.modes' set to 'author' by -r option
Verbose option not active, closing stdin and redirecting stdout and stderr
Redirecting stdout to C:\author\.\crx-quickstart\logs\stdout.log
Redirecting stderr to C:\author\.\crx-quickstart\logs\stderr.log
Press CTRL-C to shutdown the Quickstart server...

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

Exception when running form in debug mode

Hello,
appreciate any help on this.
everything is fine when oracle forms 10g is run with debug=no, but when debug=yes
throws this exception in the sun java console.
proxyHost=null
proxyPort=0
connectMode=HTTP, native.
Forms Applet version is : 10.1.2.0
java.lang.ClassNotFoundException: Execute
     at sun.plugin2.applet.Applet2ClassLoader.findClass(Unknown Source)
     at sun.plugin2.applet.Plugin2ClassLoader.loadClass0(Unknown Source)
     at sun.plugin2.applet.Plugin2ClassLoader.loadClass(Unknown Source)
     at sun.plugin2.applet.Plugin2ClassLoader.loadClass(Unknown Source)
     at java.lang.ClassLoader.loadClass(Unknown Source)
     at java.lang.Class.forName0(Native Method)
     at java.lang.Class.forName(Unknown Source)
     at oracle.forms.handler.UICommon.instantiate(Unknown Source)
     at oracle.forms.handler.UICommon.onCreate(Unknown Source)
     at oracle.forms.handler.JavaContainer.onCreate(Unknown Source)
     at oracle.forms.engine.Runform.onCreateHandler(Unknown Source)
     at oracle.forms.engine.Runform.processMessage(Unknown Source)
     at oracle.forms.engine.Runform.processSet(Unknown Source)
     at oracle.forms.engine.Runform.onMessageReal(Unknown Source)
     at oracle.forms.engine.Runform.onMessage(Unknown Source)
     at oracle.forms.engine.Runform.sendInitialMessage(Unknown Source)
     at oracle.forms.engine.Runform.startRunform(Unknown Source)
     at oracle.forms.engine.Main.createRunform(Unknown Source)
     at oracle.forms.engine.Main.start(Unknown Source)
     at sun.plugin2.applet.Plugin2Manager$AppletExecutionRunnable.run(Unknown Source)
     at java.lang.Thread.run(Unknown Source)
It s supposed to show the debug window with the host name and port number to do the attach debug in builder but instead throws the above.
if i dont mention port=xxxx in the default configuration in formsweb but just have debug=yes , the applet just crashes.

You can also check Francois Degrelle excellent answer to the same question:
Running a form in debug mode

Running AMIE in debug mode

Similar Messages

Maybe you are looking for