Recompile before existing Debug mode causes Raptor to hang

I have been able to do this a few times on 10R2, with Raptor, on Windows 2000 & XP
1) I write a small procedure or package in Raptor.
2) Compile it for debugging.
3) Set a few breakpoints.
4) Run it in debug mode within Raptor.
5) Step through to one of my breakpoints.
6) Go back and press the recompile for either normal or debug mode, without terminating/stopping the debug session.
7) Raptor hangs.
On a hunch, I opened up a SQLPlus window and tried to recompile the package with an alter ... compile while Raptor was still hung. The SQLPlus session was blocked from recompiling, and eventually it gave up.
I have found just killing Raptor can leave the a minor mess in the database, and Raptor will still have problems with that procedure/package when Raptor is restarted.
It appears that given time (more then a few minutes), the database cleans up things get back to normal.
Thanks,
Scott

This is a known bug. The session has a lock on the DB which makes the compile lock/hang.
-kris

Similar Messages

Updating Table with Triggers causes Raptor to Hang.

Received an Error Window
ORA-01000 Max Open Cursors Exceeded 1000
Vendor Code 100
This was displayed when updating a data value in a table which spawned a couple of Triggers, a before, after, and after statement trigger. What the Trigger does is when an Exchange Rate for a Date (one row), is changed the exchage_rate for every receipt is updated. The size of the table are in test and there are 100 receipts. The Echange Rate table has one record for every day between 01-JAN-2000 and 31-DEC-2050 (365.25*50) Rows. The open_cursors param in init file is 1000. Have done various scenarios and everything works fine from sqlplus. Hangs with message in Raptor, and have to kill process in windows..
When run in Sqlplus no problem with update.

I had the same problem but without triggers. I only changed some values in different records (always automatically commited) and after the third change I got this error message. At the same time I was connected with TOAD to the databse and there was no problem to change the data - so it doesn't look like a database problem.
UPDATE "BLATABLE"."KEYS" SET "BLAVALUE" = "abcdef" WHERE ROWID = 'AAA2c1AADAAAHa5AAH' AND ORA_ROWSCN = '7738949481842'
One error saving changes to table "BLATABLE"."KEYS":
Row 6: ORA-01000: maximum open cursors exceeded

Creator Hangs in debug mode

I am testing a five page web page that connects to an SQL Server database.
I am experiencing severe memory problems in debug mode. The application hangs after stepping through a some code.
The debug screen goes all grey and I cannot get it to return to normal (see the code).
I am developing on a windows XP platform and I am using Netscape 7.1 as my browser.

Not sure why you are getting the error . I just checked the link, as well as the download tab, and it works for me. Could you please try the link again.
Hot Fix 2: You can download it from update center: Launch the IDE and connect to the Update Center .
See how to connect to update center from this link:
http://developers.sun.com/jscreator/downloads/updates/index.jsp

Debug Mode "OFF" for J2E instance server0 - Caused by "Productive Use"

Dears,
    As titled, Debug fails for server0.
    I have checked the forum threads, and my problem is:
<b>Property "Productive Use" of server0 has a value "YES".</b>
    As debugging can only be available on non-productive-use server mode, I couldn't start debugging.
    Any one knows how to change "Productive Use" as "NO"?
    Thanks in advance.
    btw: The "Productive Use" value of 'SDM' is "NO", while for 'dispatcher' it is "YES".

Hi,
You can use the config tool to run the server in debug mode (running the server in debug mode will automatically set the "productive use" attribute to "off"!)
To launch the config tool, run the configtool.bat file located in \usr\sap\<SID>\<INSTANCE>\j2ee\configtool directory. In the lefthand side tree locate your server process and select it. Then on the righthand side go to Debug tab and activate debug mode for this element.
After you save the changes, you need to restart the cluster.
http://help.sap.com/saphelp_nw04/helpdata/en/cc/9cb34d9d11f74c98644df2b96b90f1/frameset.htm
Regards
Ayyapparaj

Visual Studio 2015 strange failure in debug mode

Hi,
I installed the latest vs 2015 on windows 7 (vmware) to test it compiling and running a set of applications (desktop) I have.
The compilation is ok but when I try to run one of those apps, I get this error (running the debug version):
Please note that if I run in release mode, there is no error at all!?
Following the call stack, it seems that it fails somewhere in the STL releasing a temporary string or something like that. Unfortunately, I cannot create just a small example showing the failure.
Any ideas of why will this failure be in debug mode only? Note that the call stack shows that this code:
    ~_String_alloc() _NOEXCEPT
       {   // destroy the object
       _Free_proxy();
is run from xstring and it fails calling "_Free_proxy();". Also note that this is called ONLY when _ITERATOR_DEBUG_LEVEL is defined. No such code is run in release mode.
Thanks,
G.

Hi,
I think I found the issue and here are some details, hopping that it will help others running in the same problem(s).
First, I did not have just the issue starting this thread, there was another issue related.
I have created a C++ DLL exporting common functions I used in various applications. Most of the time I used this DLL from console programs (servers). However I had two GUI programs where I also used this DLL, one based on MFC and the other on WTL.
These two programs have the issues as follows:
   When the MFC program is run in debug mode under the IDE, at exist the IDE will show a memory leak. This happened with both vs 2013 and vs 2015. This is a debug mode only issue.
   When the WTL program was run in debug mode under the IDE, it showed no problems at all when using vs 2013 but had the issue described at the starting of this thread under vs 2015. This is also a debug mode only issue.
It turned out that mfc issue was caused by a known bug in MFC where the termination code of the mfc app, is run BEFORE the termination of code of the DLL. This way the IDE give a false memory leak!! There were actually no memory leaks, just the false alarm!
I am not sure exactly what is going on in the WTL but the issue seems somehow similar in the sense that something not loaded in time from the DLL caused the problem.
The solution: For both projects in fact it was very easy to fix this issue by setting the option to delay load the DLL. That in turn will force the MFC to wait to first unload the DLL and then
there is no false leakage info! This also as I said fixed the WTL issue but I am not sure why? Anyway the WTL is no longer maintained (too bad!!) so who know?!
Bottom line: if you use DLLs from WTL or from MFC, delay load your DLLs! Otherwise you may get this nasty false flags in debug mode and the assert issue.
G.

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

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.

Strange Error During Page Load in Debug Mode (only) - Please Help!

Hi All,
Data base version: oracle 11g
Apex version: Apex 4.1.1
Webserver: Apache
Need help with how to troubleshoot a Critical problem. The following error only occurs during page load in "Debug" mode. And, only occurs on a specific page within the application. A web page is served-up containing the following message and the application is blocked from running the page. The browser's (IE 8.0) back button must be clicked to proceed outside of "Debug" mode.
"Error occurred while painting error page: ORA-06502: PL/SQL: numeric or value error: character string buffer too small ORA-06502: PL/SQL: numeric or value error: character string buffer too small"
Debug log follows:
"S H O W: application="2006" page="6" workspace="" request="" session="500549669426301"
Computation point: Before Header
...Perform computation of item: APP_SERVER, type=FUNCTION_BODY
...Performing function body computation
...Execute Statement: declare function x return varchar2 is begin return owa_util.get_cgi_env('SERVER_NAME'); return null; end; begin wwv_flow.g_computation_result_vc := x; end;
......Result = 156.9.122.214
...Session State: Save "APP_SERVER" - saving same value: "156.9.122.214"
Processes - point: BEFORE_HEADER
...Process "GET_POSITION" - Type: PLSQL
...Execute Statement: begin wwv_flow.g_boolean := :F109_POSITION_ID IS NULL and :APP_PAGE_ID != 101; end;
......Result = FALSE
......Skip because condition or authorization evaluates to FALSE
...Process "Get JARS Sifter Log File Record Count" - Type: PLSQL
...Execute Statement: begin DECLARE vcnt NUMBER := 0; BEGIN d('Get JARS Sifter Log File Record Count'); Select count(*) into vcnt From JARS.JARS_SIFTER_LOG Where moveid = to_number(:P6_MOVEID) and sifter_status IN ('F','J'); :F1000_P6_SIFTER_LOG_COUNT := to_char(vcnt); END; end;
Custom: Get JARS Sifter Log File Record Count
...Process "Set PTM Planned Trip Status" - Type: PLSQL
......Skip because condition or authorization evaluates to FALSE
...compatibility mode - do not set mime type
...compatibility mode - do not set additional http headers
...close http header
...metadata, fetch item type settings
...metadata, fetch items
Show page template header
Rendering form open tag and internal values
Add error onto error stack
...Error data:
......message: Error processing request.
......additional_info: ORA-06502: PL/SQL: numeric or value error: character string buffer too small
......display_location: ON_ERROR_PAGE
......is_internal_error: true
......apex_error_code: APEX.UNHANDLED_ERROR
......ora_sqlcode: -6502
......ora_sqlerrm: ORA-06502: PL/SQL: numeric or value error: character string buffer too small
......error_backtrace: ORA-06512: at "APEX_040100.WWV_FLOW", line 3027 ORA-06512: at "APEX_040100.WWV_FLOW", line 7867
...Show Error on Error Page
......Performing rollback
Rendering form open tag and internal values
...Unhandled Error while painting error page: ORA-06502: PL/SQL: numeric or value error: character string buffer too small ORA-06502: PL/SQL: numeric or value error: character string buffer too small
...Error Backtrace: ORA-06512: at "APEX_040100.WWV_FLOW", line 2707 ORA-06512: at "APEX_040100.WWV_FLOW_ERROR", line 185
End Page Rendering"
Thanks!
Bernard

All,
It appears that the page Javascript maximum limit size was reached. The error stopped appearing after some of the page Javascript code was removed out to Application Static Files. I wonder if there exists any "direct" indicator by the system whenever the size limit has been reached?
Again, the run error only occurred when the page was loaded in "Debug" mode.
Bernard

OC4J - Starting container in debug mode

When the container is started in debug mode, start-up messages are referring
to XAtransactions. This is causing a bit of confusion as we?re not using
distributedtransactions. Is this an internal message ? The message is:
Null: Connection XAXA Orion Pooled jdbc_oracle:thin:10.106.50.18.1521:EAGRI
allocated (pool size+ 0) .
Any help would be appreciated.

already using it. Any other suggestions?
"Simon Spruzen" <[email protected]> wrote in message
news:3b407dc6$[email protected]..
>
Try starting the jvm with -classic, if you're using the hotspot vm.
"Chris Bick" <[email protected]> wrote:
If I start weblogic6.1beta in debug mode the CPU pegs at 100% for about
4-5
minutes before it starts. Anyone else seen this?
-cb

CRM_ORDER_MAINTIAN works only in debug mode!

Hi Experts,
I am currently facing a strange issue. I am trying to add a line item to a service ticket, but the code works only in debug mode. Sample code is given below:
lv_product_i-ref_handle = '0000000001'.
lv_product_i-ref_guid = lv_header_guid.
INSERT lv_product_i INTO TABLE lt_product_i.
ls_orderadm_i-header = lv_header_guid.
ls_orderadm_i-itm_type = 'ZSG5'.
ls_orderadm_i-number_int = '0000000010'.
ls_orderadm_i-ordered_prod = 'SERVICEITEM_SG5'.
ls_orderadm_i-handle = '0000000001'.
ls_orderadm_i-mode = 'A'.
ls_orderadm_i-itm_proc_ident = 'SRVC'.
INSERT ls_orderadm_i INTO TABLE lt_orderadm_i.
ls_input_fields-ref_handle = '0000000001'.
ls_input_fields-objectname = 'ORDERADM_I'.
CLEAR ls_field_names.
ls_field_names-fieldname = 'HANDLE'.
APPEND ls_field_names TO ls_input_fields-field_names.
ls_field_names-fieldname = 'HEADER'.
APPEND ls_field_names TO ls_input_fields-field_names.
ls_field_names-fieldname = 'ITM_PROC_IDENT'.
APPEND ls_field_names TO ls_input_fields-field_names.
ls_field_names-fieldname = 'ITM_TYPE'.
APPEND ls_field_names TO ls_input_fields-field_names.
ls_field_names-fieldname = 'MODE'.
APPEND ls_field_names TO ls_input_fields-field_names.
ls_field_names-fieldname = 'NUMBER_INT'.
APPEND ls_field_names TO ls_input_fields-field_names.
ls_field_names-fieldname = 'ORDERED_PROD'.
APPEND ls_field_names TO ls_input_fields-field_names.
INSERT ls_input_fields INTO TABLE lt_input_fields.
CALL FUNCTION 'CRM_ORDER_MAINTAIN'
EXPORTING
it_product_i = lt_product_i
CHANGING
ct_orderadm_i = lt_orderadm_i
ct_input_fields = lt_input_fields
EXCEPTIONS
error_occurred = 1
document_locked = 2
no_change_allowed = 3
no_authority = 4
OTHERS = 5.
LOOP AT lt_orderadm_i INTO lv_tempvar.
lv_item_guid = lv_tempvar-guid.
ENDLOOP.
The item guid is coming as initial and no item is being added.But if i put a breakpoint in CRM_ORDER_MAINTIAN, then the guid is being generated properly. Any pointers why the code is behaving like this or someone has faced a similar issue before?
Thanks and Regards,
Rohit

Well, during debugging an implicit COMMIT WORK is executed on a regular basis. This might cause the ITEM GUID to be created during debugging.
However, normally, after CRM_ORDER_MAINTAIN, you should use the CRM_ORDER_SAVE as well. This will return a list of SAVED_OBJECTS. If all objects were saved correctly, do an explicit COMMIT WORK.
Works fine for us.....

Function Module working only in debug mode

Hi all,
The following Function Module works only in debug mode. The purpose of this FM is to create a notification and to put it in progress status. If I put a breakpoint before "CALL FUNCTION 'BAPI_ALM_NOTIF_PUTINPROGRESS'" it works. If I execute this FM without putting a breakpoint at that place it creates the notification but doesnt put it in progress status.
In other words, the last BAPI call doesnot work if I dont put a breakpoint before.
Can somebody help me to find out where is the problem?
Thanks,
Younes
FUNCTION ZFM_CREATE_NOTIF_IN_PROCESS.
""Local interface:
*" IMPORTING
*"     VALUE(NOTIFTYP) TYPE CHAR2
*"     VALUE(NOTIFHEADER) TYPE BAPI2080_NOTHDRI
*" EXPORTING
*"     VALUE(NOTIFNUMBER) TYPE CHAR12
*"     VALUE(NOTIFCURSTATUS) TYPE CHAR40
DATA: gs_bapi2080_nothdre TYPE bapi2080_nothdre,
      gt_return TYPE TABLE OF bapiret2.
The notification is created with a temporary number
CALL FUNCTION 'BAPI_ALM_NOTIF_CREATE'
EXPORTING
    notif_type         = NOTIFTYP
    notifheader        = NOTIFHEADER
IMPORTING
    notifheader_export = gs_bapi2080_nothdre
TABLES
    return             = gt_return.
READ TABLE gt_return TRANSPORTING NO FIELDS WITH KEY type = 'E'.
CHECK sy-subrc IS NOT INITIAL.
*The notication will be saved with a number which isnt temporary
CALL FUNCTION 'BAPI_ALM_NOTIF_SAVE'
EXPORTING
    number      = gs_bapi2080_nothdre-notif_no
IMPORTING
    notifheader = gs_bapi2080_nothdre
TABLES
    return      = gt_return.
READ TABLE gt_return TRANSPORTING NO FIELDS WITH KEY type = 'E'.
CHECK sy-subrc IS NOT INITIAL.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
The Notif is already created, it will be put in progress status
NOTIFNUMBER = gs_bapi2080_nothdre-notif_no.
   CALL FUNCTION 'BAPI_ALM_NOTIF_PUTINPROGRESS'
        EXPORTING
          NUMBER             = NOTIFNUMBER
          LANGU              = SY-LANGU
       IMPORTING
         SYSTEMSTATUS       = NOTIFCURSTATUS
       TABLES
         RETURN             = gt_return.

Hi Emmanuel,
Now I get your problem: you want to wait to have the commit finished! The call to BAPI_TRANSACTION_COMMIT has an optional parameter 'WAIT' which is space by default which causes only a commit. When you set this parameter to 'X' it will do a commit work and wait.
This should solve your problem!
Regards,
John.

Debugging mode in server - How does it work?

Hi
How does debugging mode in a server work ?
Is the code compiled line by line as we proceed or how ?
When we make a code change how is the hot code replaced when in debug mode and why not in normal run mode?
Why is it not necessary to restart a server when we make changes to jsp when in normal mode?
Thanks in Advance

How does debugging mode in a server work ?Just like in any othe rprogram.
Then how is it possible to change the values when
the program is running . i.e. we have a option that
we can change the values right !!
Because the debug api allows you to do that.
>
s the code compiled line by line as we proceedor
how ?
No. Line number information is stored in the.class
file, and the editor simply displays the line the
bytecode mentions. Whether bytecode and sourcecode
match is a different thing.
I had previously read that the compiler compiles
the code with break points at the beginning of every
class (for step by step method)
I agree with Rene. It happensthat you debug with the wrong source code and you will in that case notice that the debugger is saying that you are executing a line between methods.
>
>
When we make a code change how is the hot code
replaced when in debug mode and why not innormal
run
mode?I guess the executed bytecode for a method issimply
replaced in memory... the entry point was probably
stored and will be used to re-set to method entry
before running the new bytecode.
Then why is it not done when we are running the
server in the normal mode.
Why would it? What code should it replace it with?
>
>
Why is it not necessary to restart a server when
we
make changes to jsp when in normal mode?
Because the server can notice the change andunload
and reload the class.
I meant that when the jsp is compiled the servlet
is created when i run the server right.(i'm not
sure).
So when I change the code and without restarting the
server I run a jsp file it reflects the changes...
HOW??
Because some servlet runners can be configured to check changes on disk, and recompile if needed.
Kaj

Performance Diference between debug mode and release mode

Hi ,
I have been running an C++ multithreaded application with below technical specification on Production for more than an year.
OS - Solaris 10 , Opteron
Compiler - Sun Studio 11
Bit Mode - 64
I wanted to know what is the difference in the debug mode of an C++ application compiled with -g option and a release mode compiled with an optimization apart from the size of the binary and availability of debug information in case of a crash.
1) Does it degrade the performance of the application? If yes by what extent?
2) Does it use more memory?
3) Will switching from Debug to Release mode with some optimization coupled with any kind of risk like byte guard etc which could lead to dumps and all? If yes what could those be?
4) Which optimization level should be used?
Regards,
Ankur Verma

If you compile without any optimization (with or without -g), you will see a noticeable difference in performance in most programs compared to compiling with a reasonable level of optimization. How much difference depends on the nature of the program, and what percentage of time is spent in code regions that can benefit from the code improvements.
If you add -g, function inlining is disabled, which can dramatically reduce program performance. You can't debug a function that is generated inline, which is why this option disables inlining. (The +d option also disables inlining.)
If you use -g0 instead of -g, function inlining is preserved.
If you use -g0 with optimization, you get the advantages of optimization while still allowing limited debugging. (Local variables are not visible.) Beginning with Sun Studio 12 update 1, the current release, -g with optimization enables function inlining, so the effect of (for example) "-O -g" becomes the same as "-O -g0".
A few optimizations are disabled with -g or -g0, the exact difference depending on the compiler release and patch level. Most programs won't see a difference in performance.
Since you are running on Solaris 10, you should upgrade to the current release, Sun Studio 12 update 1. You will get many improvements and some new diagnostic tools. The new release is a drop-in replacement for Studio 11. You don't have to recompile any existing binaries, but you will want to recompile to get improved performance.
[http://developers.sun.com/sunstudio/]

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

How to fill internal table with no data in debugging mode

Hi all,
I modified one existing program.Now I want to test it.I am not given test data.So in the middle of my debugging, I found that one internal table with no data.My problem is how to fill that internal table with few records in that debugging mode just as we change contents in debugging mode.If I want to proceed further means that internal table must have some records.
Please I dont know how to create test data so I am trying to create values temporarily in debugging mode only.
Thanks,
Balaji

Hi,
In the debugging do the following..
Click the Table button..
Double click on the internal table name..
Then in the bottom of the screen you will get the buttons like CHANGE, INSERT, APPEND, DELETE..
Use the APPEND button to insert records to the internal table..
Thanks,
Naren

Recompile before existing Debug mode causes Raptor to hang

Similar Messages

Maybe you are looking for