Entering in debugging mode

Hello
I'm experiencing the following issue :
Iw32 is called by a call transaction in a customer program. In the process, a standard function (pm_partner_update)
ends with an abap runtime error SAPSQL_ARRAY_INSERT_DUPREC.
Instead of the short dump report, the enduser is entering in debugging mode, with the cursor placed on the failed command. Although he cannot do anything because
he has no debugging authorizations, is it possible to prevent the debug screen display?
Regards,
Philippe

we need to pass all the three key fields of IHPA table to avoid this duplicate entry error as it gets generated when you try to update duplicate records to master table . In my case i used I_count parameter of ihpa table to increament the counter . In each case if we do not use counters in that case it is bound to give you exception .so make sure you are not updating any duplicate entry .

Similar Messages

WebView weird rendering issue (Color rectangles) - Debug Mode

Hi,
i got a problem with a JavaFX Webview.
Everything loads fine, but every single Element in the DOM of the page (including the body) is overlayed with a random colored rectangle when hovered.
After a few seconds the entire page is renders unreadable and is only a freaky mix of colors.
It does work without problems in the JavaFX Ensemble Example so i think it can't be a javafx probleme but i am doing something wrong somewhere else in my application.
The initialisation code is the same as in the example:
webview = new WebView();
previewStage.getChildren().add(webview);
final WebEngine webEngine = webview.getEngine();
webEngine.load("http://www.google.de");
Thought it might be an stylesheet issue, but i removed all stylesheets and it still looks the same.
I attached some pictures how it looks.
http://www.tinyuploads.com/images/31lf1b.png
http://www.tinyuploads.com/images/UxK8wZ.png
I appreciate any help.
Thank you!

THANK YOU VERY MUCH.
This solved my problem and it was driving me crazy. :-)
For Future reference:
WebView enters a debug mode when logging is set to a level higher than FINEST.
You can change it for the particular class using these lines:
Logger logger = Logger.getLogger( WCGraphicsPrismContext.class.getName() );
logger.setLevel( Level.OFF );

Lm3s8962 cannot enter debug mode

Hello,
I am developing an application on my luminary lm3s8962 with labview for ARM, I have an home made PCB with this ARM and sensors.
I have 2 PCB's of the same.
My problem is,
instead of a 8 MHz crystal I have a 8 MHz oscillator (single ended) so I see that my RTC is not good, I can see this with GPS timing.
but using timer0 with interval 1 sec and update a counter works good!?
I tried to make some changes in the startup file with the clock configuration:
        ; set the system clock to run at 50 MHz
        ; SysCtlClockSet(SYSCTL_SYSDIV_4 | SYSCTL_USE_PLL |
        ;                SYSCTL_XTAL_8MHZ | SYSCTL_OSC_MAIN);
        LDR        R0, =0x01C00380
        BL        SysCtlClockSet
Looking in the SysCTL I see other crystal values, like 16 MHz. used value: #define SYSCTL_RCC_XTAL_16MHZ   0x00000540 // 16.0 MHz (USB), instead of 0x380
I know this is not supported, but I want it to give it a try.
I build it and flash it, but now my debugger says:
Cannot enter memory and cannot enter debug mode.
I did some reading on the internet and it says that because 16 MHz is not supported it goes into deep sleep.
I don't know if this true..
My other PCB works fine, this one is not flashed with the wrong clock.
my question is:
first priority:
Can I prevent that my program starts up in my arm, so I can flash it with the good clock configuration. OR
Can I erase the flash (with out ULINK2) in some way, so that no program starts up and I can flash my ARM.
second priority:
Maybe someone knows how I can get the right RTC with my 8 MHz oscillator, I need a correct clock in ms.
Thank you in advance,
Wouter
Wouter.
"LabVIEW for ARM guru and bug destroyer"

Hi Wouter,
The questions about the flashing can be found via the following link.
http://www.keil.com/support/man/docs/ulink2/ulink2_su_flashdownloadcfg.htm
(right click on the target and click on Show Keil uVision)
About the hardware configuration you can better ask uVision, since they know more about Hardware.
Maybe this link helps.
http://www.keil.com/support/man/docs/rlarm/rlarm_ar_config.htm
Regards,
Bas van Dijke
NI Netherlands

Restart the server in debug mode: How to drop saved passwords?

In NWDS server pane, I entered a wrong password when trying to restart my SAP AS Java in debug mode. Now I only get exceptions "com.sap.enginemanagement.UnauthorizedException: Incorrect login information provided" without a chance of changing the entered credentials. Restarting NWDS didn't work.
Any ideas?
Thx,
Christoph

Hi Christoph,
are you talking about the "Java EE" perspective and the "Servers" view within it? I tried it out and it does not behave properly.
Try the "SAP Management" perspective. Within the left hand tree open your system, expand the instance starting with "J..", expand the "AS Java" node and select the "Process Table" node. In the right hand table select the server0 process and chose from the context menu "Start Debug Session".
The SAP JVM offers some extra debug options. Expand the "Expert Mode" in the modal dialog. If you want to debug web applications select "code isolation" and unselect all other options. A password dialog will appear and you must enter the credentials for the operating system user, not for the AS Java administrator.
One table column is labeled "Debug", there you can see the currrent debug port.
Either you start now a "Remote Java Application Debug" debug session or you have a Java EE project and can create a "SAP Application" debug session.
Anyway to see your application threads in the debugger you have to access your web application with a special debug URL.
If your URL looks like this: "http://localhost:50000/myapp" you have to insert a debug token beween host part and the path and the URL becomes "http://localhost:50000/@@@DEBUG@@@/myapp". If you miss to modify the URL you will not see any thread.
If you want to get a "normal" debug behaviour just deselect all options in the debug dialog. You will see all threads, you do not have to modify your URL, but the server will restart after you detached the debugger.
Hope this helps.
Best Regards, Stefan
Edited by: Stefan Bodenstein on Oct 1, 2008 12:00 PM

CRM_ORDER_SAVE works properly only in debug mode

I have a scenario where I'm creating two order documents (using CRM_ORDER_MAINTAIN and CRM_ORDER_SAVE), then linking them with function module CRM_CREATE_BREL_TO_CONTRACT. After calling CRM_ORDER_SAVE and before CRM_CREATE_BREL_TO_CONTRACT, I "commit work and wait" and call CRM_ORDER_INITIALIZE. When I set a breakpoint immediately before CRM_CREATE_BREL_TO_CONTRACT (and thus have to pass through debug mode), CRM_CREATE_BREL_TO_CONTRACT works with no problem. If I don't pass through debug mode, it fails and returns the flag EV_LOCKING_PROBLEM = true.
I have added "wait X seconds" and have even added a while loop that calls CRM_ORDER_CHECK_CHANGE_ALLOWED. But when I don't enter debug mode, this while loop runs forever.
Does anybody know what's happening here? I suspect there is some kind of problem with document distribution, but I'm not sure.
Many thanks,
Tom Peng

Hello Tom,
As you may already known, the lock is added in FM CRM_CREATE_BREL_TO_CONTRACT with the following coding:
      IF ls_active_switch-lock_contract <> gc_act_switch-inactive.
*       Lock contract
        CALL FUNCTION 'CRM_ORDER_ENQUEUE'
          EXPORTING
            iv_guid           = iv_contract_header
          IMPORTING
            ev_already_locked = lv_already_locked
          EXCEPTIONS
            foreign_lock      = 1
            system_failure    = 2
            distributed_lock = 3
            no_change_allowed = 4
            transferring      = 5
            OTHERS            = 6.
        IF sy-subrc <> 0.
Here system checks whether activ_switch is active. If yes, the error issued.
Thus you need to pass the parameter t_active_switch with value false when call FM crm_order_save.
Hope this information could be helpful.

How to skip a selection screen mandatory field in debugging mode with out changing the code?

Hi Team,
In my report there is two fields on selection screen, one is obligatory field , but i just want to execute the report(for testing per pus) with out entering the data for the mandatory field with out changing the code. could u let me know which event and how to debug the report. or else in debugging mode how can i change that field as non mandatory field.
Regards,
Venkat.

If the value is not of importance how come it became obligatory in your program?
Any how you can do one thing...Put some value in your obligatory field, put a debugger point where you are interested in and use the pencil tool to change the value of the field while debugging.
Regards,
Philip.

Firefox UI becomes completely unresponsive in debugging mode.

I'm using Firefox for web development, and set breakpoints with the `debugger` keyword, or the breakpoint UI in the "Debugger" section of the "Web Developer" tools. I remember that used to work on older versions, but recently it started failing.
Now, when I enter debugging mode (i.e. hit a breakpoint), the debugger UI shows, but it is completely unresponsive: the mouse cursor doesn't change when I hover over any widget, and clicking does nothing.
The only way to get any response is CTRL-r refresh which *sometimes* works, as well as closing the entire Firefox window. Of course, that means I can't actually use it to debug.
I'm on Xubuntu 13.10, running latest stable 64bit Firefox (3.1.1). I also verified the exact same bug on the nightly binary release (firefox-36.0a1.en-US.linux-x86_64.tar.bz2) as well as the recently released Developer Edition (firefox-35.0a2.en-US.linux-x86_64.tar.bz2).

HI dunpealer,
Please do file a bug on this and make sure to put version 35 and os linux on bugzilla.mozilla.org.
I am sorry it took so long to get back to you, I also can reproduce this. If you have any questions about bugzilla we are happy to help here as well.
Thank you!

Sun Ray Connector proxy i on debug mode - VDI 3.1.1 -

Hi,
On each connection to a windows session with VDI I use the Sun Ray Connector Proxy, each user launch a daemon called uttcpd everytihnings is ok but this daemon is launch on debug mode so my /var/ad/messages is full of usesless debug message. I don't find any option or configuration file on the doc to change the daemon logging mode.
Thanks per advance for your help,
Sylvain.

I have the same issue . . .
1. Sun Ray 5 (Sun Ray 4.2)
2. SRWC 2.2
3. Solaris 10 u9 X86 on two x2200
4. Terminal Server on Win2K3 R2 Standard x64 Edition SP2
I have a handful of users and they all logon the same way, which is to enter username & password then I have the following lines at the end of the users' individual .dtprofile file . . .
<begin snip>
DTSOURCEPROFILE=true
/opt/SUNWuttsc/bin/uttsc -b -m -O -u uname 192.168.100.29
exit
<end snip>
Of course 'uname' is actually the user name followed by the Terminal Server IP address and as you can see I am using the '-O' option, but every morning all the users on a server have their Sun Ray sessions reset and I find this in the messages file . . .
Mar 16 09:38:31 sunraya Sun Ray Connector proxy:[12941]: [ID 855542 user.error] Child closed socket prematurely, session shutdown
. . . . Using cron, I reset the Sun Ray service twice a day on both servers at 7AM and 7PM . . .
# cat /sunray-restart.script
# This is to restart SunRay 5 service due to
# what I think may be a memory leak that disconnects
# the SunRay Windows Connector every day
/opt/SUNWut/sbin/utrestart -c
echo "#" >> /var/adm/messages
date >> /var/adm/messages
echo "#" >> /var/adm/messages
echo " RESTARTING SUNRAY SERVICE " >> /var/adm/messages
echo "#" >> /var/adm/messages
echo "#" >> /var/adm/messages
. . . But this does not appear to having an affect.
I will be looking around the forums for any other bits of information about this. The "Known Issues" can probably be found in the Release Notes.

Debug-mode and function calls

Hi there,
I'm coding a program in SE38 in a BW environment and there is a function call made (RSDRI_INFOPROV_READ). It seems that the table returned by this function won't accept double entries (which should be the case for standard tables), however, when I execute my program in debug mode, it does everything like it should. Anyone knows why it doesn't work when i choose execute as background job? It's hard to find what's wrong since in debug all goes well...
thank you,
Tom

Why not debug the program in background running？You can add a endless loop before the code you are interested in, and then enter debug mode to jump to the focus code at background job console.

Exit Debug Mode on M92z?

I was monkeying around in the OSD trying to see if there was a reason my newly delivered M92z's speakers wouldn't work. For the heck of it, I selected Debug Mode from the Advanced Settings menu and the black box appeared. Now it comes up whenever power is on and eventually just flashes a0... How do I exit Debug Mode?!? I've removed power for 5 minutes and pressed the OSD buttons to no avail.
The sound problem turned out to be simply unplugged speaker connection btw...
Edit: Resolved, delete if desired...

Debug mode is entered using the OSD buttons on the front. When the computer has started, press the 'Exit OSD' button (the left-most), then go back into the OSD -> Advanced Settings -> Debug Mode -> Disable.

Sprint BlackBerry 8830 - how do we get in to debug mode...?

I have searched for two days everywhere and can not locate how we enter in to debug mode on the 8830.
I need access to the Rx Ec/lo and the SID#, currently I can only get signal strength in the home screen by pressing the ALT+NMLL (changes the graphical signal indicator to the numerical one, i.e. -80)
Please, I could really use some help with this so we can diagnose the repeaters on our corporate campus.
Thanks,
J
Solved!
Go to Solution.

Well, to answer my own question, I have now found the answer.
Unfortunately, the 8830 and some of the other newer BlackBerrys do not make it easy to get this type of engineering information.
You must:
Have a login/password to https://www.blackberry.com/EngineeringScreens/ (updated 5/30/2008)
On the BlackBerry pres ALT+CAP+H and leave it on this screen.
Once logged in to the link on #1, you will be asked to enter your PIN#, Uptime and Zip code of where your device is.
You will then receive a unlock code that is specific to this information (if you exit out of this help screen on the blackberry, the uptime number will be different thus your code will be different.)
Then enter the unlock code on the BlackBerry, holding the ALT key for numbers, capitals are not necissary.
This will give you access to the Trace Mode Engineering App
Select "Radio Engineering" screen
Select "CDMA Engineering" screen
Select "Operational Info" (2nd line ec/io, 3rd line rss)
Scroll down to "Neighbor Set Details" and get 1st line Active Pilot, 2nd through 20th will give Neighbor sites with ec/io for each.
*This code will only work for 30 days, then you will need to get a new code in the same way.
I hope this helps everyone!
Message Edited by mobilejray on 05-30-2008 02:12 PM

Error when starting Weblogic in debug mode

Hi there
Has anyone experienced any difficulties when starting weblogic in debug mode.
More specifically, it cannot start correctly because it thinks that another instance
is using the same port (definately not the case).
Any clues/suggestions are greatly appreciated.
Error log follows:
<Mar 18, 2002 7:42:32 AM GMT+10:00> <Emergency> <WebLogicServer> <Unable to create
a server socket for port: 8320. java.net.BindException: Address already in use
Perhaps another process is using port 8320.>
<Mar 18, 2002 7:42:32 AM GMT+10:00> <Notice> <WebLogicServer> <SSLListenThread
listening on port 8321>
<Mar 18, 2002 7:42:32 AM GMT+10:00> <Emergency> <WebLogicServer> <The WebLogic
Server is no longer listening for connections. You should probably restart it.>
<Mar 18, 2002 7:42:32 AM GMT+10:00> <Alert> <WebLogicServer> <Server shutdown
has been requested by system>
<Mar 18, 2002 7:42:32 AM GMT+10:00> <Alert> <WebLogicServer> <The shutdown sequence
has been initiated.>
<Mar 18, 2002 7:42:32 AM GMT+10:00> <Info> <WebLogicServer> <Server shutdown is
commencing NOW and is irreversible.>
<Mar 18, 2002 7:42:32 AM GMT+10:00> <Error> <Performance Pack> <Unable to load
performance pack, using Java I/O.
java.lang.ThreadDeath
at java.lang.Thread.stop(Thread.java:581)
at weblogic.t3.srvr.T3Srvr.die(T3Srvr.java:764)
at weblogic.t3.srvr.T3Srvr.waitForDeath(T3Srvr.java:507)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:171)
at weblogic.Server.main(Server.java:35)

Thanks for the suggestion.
Unfortunatley the port is definately free/available during startup.
Stephane Kergozien <[email protected]> wrote:
Maark,
Before starting your server, please could you check that the port is
not used by one
other process. You can use the netstat command to do this.
Regards
Stephane
Mark wrote:
Hi there
Has anyone experienced any difficulties when starting weblogic in debugmode.
More specifically, it cannot start correctly because it thinks thatanother instance
is using the same port (definately not the case).
Any clues/suggestions are greatly appreciated.
Error log follows:
<Mar 18, 2002 7:42:32 AM GMT+10:00> <Emergency> <WebLogicServer> <Unableto create
a server socket for port: 8320. java.net.BindException: Address alreadyin use
Perhaps another process is using port 8320.>
<Mar 18, 2002 7:42:32 AM GMT+10:00> <Notice> <WebLogicServer> <SSLListenThread
listening on port 8321>
<Mar 18, 2002 7:42:32 AM GMT+10:00> <Emergency> <WebLogicServer> <TheWebLogic
Server is no longer listening for connections. You should probablyrestart it.>
<Mar 18, 2002 7:42:32 AM GMT+10:00> <Alert> <WebLogicServer> <Servershutdown
has been requested by system>
<Mar 18, 2002 7:42:32 AM GMT+10:00> <Alert> <WebLogicServer> <The shutdownsequence
has been initiated.>
<Mar 18, 2002 7:42:32 AM GMT+10:00> <Info> <WebLogicServer> <Servershutdown is
commencing NOW and is irreversible.>
<Mar 18, 2002 7:42:32 AM GMT+10:00> <Error> <Performance Pack> <Unableto load
performance pack, using Java I/O.
java.lang.ThreadDeath
at java.lang.Thread.stop(Thread.java:581)
at weblogic.t3.srvr.T3Srvr.die(T3Srvr.java:764)
at weblogic.t3.srvr.T3Srvr.waitForDeath(T3Srvr.java:507)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:171)
at weblogic.Server.main(Server.java:35)--
Regards,
Stephane Kergozien
BEA Support

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

Can not view contents of variable in debug mode (version 1.1.1.5.0)

Hi
I am running on WebLogic 11R1 and using OEPE 1.1.1.5.0.
When Fast swap is enabled and I run WebLogic in debug mode using OEPE I can not view the contents of variables with the Eclipse debugger. I get the message "Expressions must contain either an expression or a block containing a well formed statement"
However, if I disable Fast swap, i can view the variable within the Eclipse debugger
Has anyone else had this problem?
Regards
Steve H

Small correction... the soon-to-be-released version of WebLogic Server that Danny was referring to is 11gR1 PatchSet 2 or 10.3.3.

FlashBuilder 4.7 will not run in Debug mode with BlackBerry 10 simulator

We have developed an app that has been released both for Apple and Android working well.
When trying to do the same for BlackBerry it was rejected because it did not start at all.
The App that runs fine on the BlackBerry simulator in the "run configurations mode".
However when I try to run it in Debug mode it will not start at all. Just flashes and simulator goes back to main menu.
The debugger will after a while time out since it cannot connect to the app running on the simulator.
BlackBerry 10 Simulator runs under vmWare Fusion.
Anyone seen this before?

Hi, Silence04. Welcome to the Discussions.
You had serious disk directory corruption. That can also cause corruption in OS files: while Disk Utility or DiskWarrior may fix the directory, if the directory corruption resulted in OS files being damaged — as it appears to be in this case — then you can't avoid an Archive and Install. For important tips on this, see my "General advice on performing an Archive and Install" FAQ. Perform the steps therein in the specified order.
Good luck!
Dr. Smoke
Author: Troubleshooting Mac® OS X
Note: The information provided in the link(s) above is freely available. However, because I own The X Lab™, a commercial Web site to which some of these links point, the Apple Discussions Terms of Use require I include the following disclosure statement with this post:
I may receive some form of compensation, financial or otherwise, from my recommendation or link.

Entering in debugging mode

Similar Messages

Maybe you are looking for