Debug mode: attach to running process

Hi all,
Is there anything different in how one might remotely attach to a running
portal server? I've added the following line
(-Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,server
=y,suspend=n,address=8999) which worked well under WLS 7.0 and a separate
app not related to Portal 7.0 in any way.
While I am able to connect/attach to the remote VM under IntelliJ, none of
my breakpoints actually break. I am able to view output to the console, so
I know the line in question is getting executed. I assuming that setting up
the Portal server to operate in debug mode is exactly the same as setting up
WLS 7.0 to operate in debug mode, but so far it doesn't seem to be the case.
TIA
Michael.

i haven't done this in awhile, but i have notes that use some of these options...
transport=dt_shmem,address=localhost,server=n,suspend=y
transport=dt_shmem,address=ebcc,server=y,suspend=y
transport=dt_socket,address=localhost:8000,server=y,suspend=y
good luck!
-tanya
"Michael Morett" <[email protected]> wrote:
Hi all,
Is there anything different in how one might remotely attach to a running
portal server? I've added the following line
(-Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,server
=y,suspend=n,address=8999) which worked well under WLS 7.0 and a separate
app not related to Portal 7.0 in any way.
While I am able to connect/attach to the remote VM under IntelliJ, none
of
my breakpoints actually break. I am able to view output to the console,
so
I know the line in question is getting executed. I assuming that setting
up
the Portal server to operate in debug mode is exactly the same as setting
up
WLS 7.0 to operate in debug mode, but so far it doesn't seem to be the
case.
TIA
Michael.

Similar Messages

Remote Enabled function module of SAP working - debug mode but not run mode

Hi,
When a remote function module is called from Java a message should get thrown from the function module which the FM is throwing but Java is not able to fetch the error. This problem is coming in execution mode but if we are in debugging mode and go to the function module remotely the error is getting triggered.
Please suggest the solution to the problem.
Thanks,
Abhishek

Hello
try something like this
try {
JCO.Client.execute(myFunction)
} catch (JCO.AbapException ex) {
System.out.println ("ABAP Exception: " + ex.getKey() + " " + ex.getMessage());
the problem is, that JCo ABAP Exceptions are subclasses of java.lang.RuntimeException so the Java Compiler doesn't force you to catch them
regards franz
reward points if useful

OLE Program works in debug mode fails when run from F8

Hello,
I have implemented a code from this forum for sending documents to printer, as below, but although it works well in debug mode, it fails when I execute directly from SE38? Any idea?
Best Regards,
Didem GUNDOGDU
CREATE OBJECT gs_word 'WORD.APPLICATION'.
SET PROPERTY OF gs_word 'Visible' = '0'.
CALL METHOD OF gs_word 'Documents' = gs_documents .
CALL METHOD OF gs_documents 'Open' = gs_newdoc
EXPORTING
#1 = p_filep .
CALL METHOD OF gs_word 'ActiveDocument' = gs_actdoc.
CALL METHOD OF gs_actdoc 'PrintOut' .
CALL METHOD OF gs_word 'Quit' .

Hi Didem,
Just a suggestion: could you print syst-subrc after each method call? Perhaps that can give you a clue.
Regards,
John.

JApplet run in Debug mode but not in Run Mode in JDev3.1

Hi All
I am having a problem in running a JSP file which contain an JApplet. When I choose Run from the jDev, the applet seems to take a really long time to load and finally failed to load itself.
However when i choose run from debug mode, the jsp run perfectly by displaying the applet.
Any idea why?
thanks for any help
ka

Hi All
I am having a problem in running a JSP file which contain an JApplet. When I choose Run from the jDev, the applet seems to take a really long time to load and finally failed to load itself.
However when i choose run from debug mode, the jsp run perfectly by displaying the applet.
Any idea why?
thanks for any help
ka

Could not run flex app in debug mode

All of a sudden I am having issue running my flex app on debug mode that was running fine before. When ever I launch my app on debug mode, I get a popup information that says,
"This file you chose is not inside a project, so many Flex Builder features will be disabled."
I asks me to create a new flex project. I have tried to close the FB and relaunch it, restarted my machine couple of times, cleared the browser cache. nothing seem to work?
What is the issue with this? I have never come across this issue before. Any help will be highly appreciated. Thanks.
KM

Try asking on the Flash Builder forum

Debug mode in forms6i?

Hi,
Was wanting to know how do i use/run my form in debug mode.....how do i go about it once i click the debug mode icon and run the form?
Thanks,
Aparna.
null

Hello Aparna
check out this site http://otn.oracle.com/products/forms/pdf/275198.pdf
you get to it through http://otn.oracle.com/docs/products/forms/doc_index.htm->forms->trouble shoot(pdf). This is the technical white paper.
hope this might help you.
have a nice day
murali
<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by Aparna Kane ([email protected]):
Hi,
Was wanting to know how do i use/run my form in debug mode.....how do i go about it once i click the debug mode icon and run the form?
Thanks,
Aparna.<HR></BLOCKQUOTE>
null

Cannot read properties files in debug mode .....

I am using JDeveloper 10g (10.1.3.0.4) and cannot seem to read properties files in debug mode, while it runs fine in Run (non debug) mode!!
For code like this:
Properties props = new Properties();
String dbPropsFile = "/pol_main.properties";
InputStream is;
is = this.getClass().getResourceAsStream(dbPropsFile); <---- ERRORS HERE!
props.load(is);
I get error messages like:
"Unable to find source file for package oracle.classloader, filename PolicyClassLoader.java".
Cannot go any further.
I am using the "hotspot" virtual machine under Project debug options. Using Sun's
JDK 1.5 update 6 with Ojvm installed.
Thanks.

I think I figured out something. In jDeveloper 10.1.3, open your project properties and click on the Run/Debug treeview branch. Now Edit the Run Configuration you are using (mine is Default) and check the Run Directory. If I change this to be the root of my source, which is one level down from my .jpr file, it now uses my standard path and finds my files. I suppose you could also change this to use the classes directory as the root as long as your props files were there too. My problems seem to be the result of my project root being one folder higher than my source root due to the way our project was imported from CVS. --Ed

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

JDeveloper 11.1.2.1.0 Hangs in Debug Mode Running in Windows 7 OS

Hi All,
i am working with JDeveloper 11.1.2.1.0 version,intel core i3 -2120 CPU,@3.30GHZ,4GB RAM, Windows 7 32 bit OS
i am facing Jdeveloper Hangingness when loading BTF inside a popup and making a call to java code on any action if any debug point is avilable inside java file,JDeveloper is getting hanged and the only way to come out of this issue is by killing the process and restarting the JDeveloper.
certain cases when integrated server is started with debug mode(intial startup ) also Jdeveloper is getting hanged and there is no way to get out of this except restart.
if i see memory parameters from Java VisualVM console
Heap is avilable
and the other process are running with out any issue.
is this problem is with configuration settigns ?
what steps/settings/patches i need to follow to get out of this problem ?

is this happening after removing the system folder also?

How to DEBUG a function module running in background mode? Please help!

Hi Experts,
   I am calling a function module in my ABAP code in background module using the following syntax:
CALL FUNCTION 'YBBC2_CREATE_SNAPSHOT' IN BACKGROUND TASK
          TABLES
            itab_std_format_inv = itab_std_format_inv
            itab_snapshot_inv = itab_snapshot_inv.
        COMMIT WORK.
If I put the breakpoint in the CALL FUNCTION line and execute the program, the debugger does not take me to the valled function module. This may be because I am running the function module as background task.
I cannot comment this "IN BACKGROUND TASK" statement as well since i am debugging in Quality system where I don't have change access.
So how to DEBUG a function module running in background mode? Please help!
Thanks
Gopal

Hi,
You could try to use the following trick:
(1) Put an endless loop into the coding of your function module where you want to start debugging, e.g.
DATA:
    lx_exit_loop(1)     TYPE c.
lx_exit_loop = ' '.
DO.
    IF ( lx_exit_loop = 'X' ).
      EXIT.
    ENDIF.
ENDDO.
(2) Call your function module in background task
(3) Call transaction SM50 and search for the background process.
(3) Choose from menu Program/Mode -> Program -> Debugging
Now you the debugger should bring you right to your endless loop. Set lx_loop_exit = 'X' in the debugger and continue (F5 or F6).
<b>Reward points</b>
Regards

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 the forms under debug Mode?

Hi,
I run my form under debug mode by introducing a break point on a trigger. But i am receive the following error how to solve this issue.
JVM aborting and followed by the following one.
FRM-92101: There was a failure in the forms server during startup.
This could happend due to invalid configuration.
Please look into the Web-server log files for details.and additional information from Java console.
proxyHost=null
proxyPort=0
connectMode=HTTP, native.
Forms Applet version is : 10.1.2.0
oracle.forms.net.ConnectionException: Forms session <5> aborted: unable to communicate with runtime process.
     at oracle.forms.net.ConnectionException.createConnectionException(Unknown Source)
     at oracle.forms.net.HTTPNStream.getResponse(Unknown Source)
     at oracle.forms.net.HTTPNStream.doFlush(Unknown Source)
     at oracle.forms.net.HTTPNStream.flush(Unknown Source)
     at java.io.DataOutputStream.flush(Unknown Source)
     at oracle.forms.net.StreamMessageWriter.run(Unknown Source)I am running on my standalone machine.
Where and what file i want to look into this to solve this issue.
Good help will be appreciated. Thank in advance.
kanish

Kanish,
Lets start with a few of the basics, shall we. What JVM are you using (Jinit or Sun JRE and the version)? Based on the error you posted, I can infer that you are using Forms 10.1.2.0? Are you running a custom configuration in the formsweb.cfg and default.env? This could be the cause if you have modified the CLASSPATH setting in the default.env excluding core .jar files.
Typically, the FRM-92101 error is caused by a Java error; either a .jar is not found or invalid or not compatible with JVM, etc.
Have you tried clearing your Java Cache to check for a corrupt .jar?
Hope this helps,
Craig B-)
If someone's response is helpful or correct, please mark it accordingly.

Running smq2 queues in debug mode

Hi,
Can anyone tell me how to successfully run an inbound queue in debug mode.
Following are the steps undertaken.
I locked the queue in SMQ1. The Queue is set to STOP state.
I then triggered an sBdoc flow into CRM.
I am expecting the sBdoc to be in an intermediate state, but to my surprise it is coming as Fully Processed.
At this point, setting Debug mode in smq2 and Unlocking the queue does not help me analyse the bdoc/process flow as the bdoc is allready processed.
Any inputs in this regard would be helpful.
Thanks & Regards
Ron.

Hi Ron,
Please check below blog, hope it helps u.
Regards,
Deven
/people/lokesh.aggarwal/blog/2008/02/27/debugging-crm-middleware--sales-document

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

Debug mode: attach to running process

Similar Messages

Maybe you are looking for