Debug Mode -WebDynpro

Hi,
I configured everything for debugging. I set a breakpoint and it works but where can i go and see returned values?.
Also when the breakpoint hits while debugging how do i step line by line or resume or move onto next line. When my debugger hits the breakpoint i cannot resume it is stuck.

Hi zxcheng,
[Start Server in Debug Mode|How to start server in debug mode by default;
[Web Dynpro for Experts|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/media/uuid/3178ae74-0701-0010-ba8d-e3ca9f1edc1e]
I guess the above links will also help you.
Regards
Sid

Similar Messages

SRM 7.0 - Unable / How to get into DEBUGGING mode in BADI

Hello SAPions,
I am unable to get into debugging mode from WebDynpro Portal screen to R/3 BADI in SRM 7.0 .
I placed a breakpoint in the BADI, and logged into the portal screen.
However, in SRM5.0, to get into debugging mode from ITS, we place a break point in the BADI, when we browse the ITS link from the IE browser, we will be able to get into debuggin mode.
Any other way ?
Regards,
Ashwin.

Hello,
Please check the following:
1. Application server name, the SAP GUI and the portal should be logged into the same application server.
2. You should be logged in with the same User in both SAP GUI and the Portal.
3. External debugging should be enabled for the User in SAP GUI.
4. Also try checking the check box , IP Matching . This can be done as below:
Utilities -> Settings -> ABAP Editor -> Debugging -> IP Matching.
Also please check the following in the above link , if you have the same user name here with which you have logged onto Portal and the New Debugger Radio Button is Selected.
Hope this helps.
Best Regards,
Sapna

Error while configuring Debugging for WebDynpro Application

Hi Experts,
I am trying to configure Portal server for debugging a WebDynpro application.
In NWDS , in Debug configuration
When i tried to add my Webdynpro Project and application under Debug tab , No problem.
But when i checked J2EE Engine tab : it showed the following error.
[J2EE Engine]: the selected server node does not run in restricted load balancing mode, please configure it correctly so that the URL extention can be used
And ignoring it when i started debugging the application , the URL was formed like this :
http://<host>:50000/@@@DEBUG@@@7672950/webdynpro/dispatcher
/local/WDtest/WDtest?SAPtestId=1
with the error : The requested resource does not exist.
Details: Go to main page of this application!
Can anybody help me to fix the configuration.
Regards,
Ashish Shah

Hi,
To configure to the debugging mode... follow the steps:
1. Select "SDM" from J2EE engine (To get this view navigate thru Window--> Show View --> J2EE Engine)
2. Make a right click on "SDM" and choose "Enabling Debugging of Process"
3. Now, Navigate to Run --> Debug --> Select your Project as "Webdynpro Application" and click "new" button
4. Now give some name and Click BROWSE to select ur project and then click APPLY and DEBUG
Or if u use 2004s, then u can do the settings in Portal itself...which gives u more clear information... follow the link
<a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d0cb32c5-36a7-2910-2c9b-ba4a5bbdbb56">WebDynpro Java Debug Configurator</a>
Hope it helps...
Regards / Guru

Problem with Debug mode and SLD

Using the config tool, we have turned the Debuggable flag to 'yes' and set the Debug mode to OFF. Now from the studio, when I enable debugging for the process, the server0 stops successfully and restarts successfully. However, during the restart, the SLD service errors out and does not get started. It encounters the following exception. I can verify the error in std_server0.out
With erred SLD service, when I try to deploy and run the webdynpro application from studio, the deploy fails with the same exception.
We tried all kinds of restart (of the engine\server instance), debuggable and debug mode setting permutations, but not successfull. (debug port is 50021)
We are having remote debug server setup (not local).
Does anybody have any suggestions???
The exception we get is:
Finished with warnings: development component 'CreateOrder'/'local'/'LOKAL'/'0.2007.11.26.14.33.54':Caught exception during application startup from SAP J2EE Engine's deploy service:java.rmi.RemoteException: Error occurred while starting application local/CreateOrder and wait. Reason: Clusterwide execption: server ID 3775750:<Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='com.sap.engine.services.deploy.container.DeploymentException: <Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='Implied start failed for dependency :local/CreateOrder -> service:sld', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key Implied start failed for dependency :local/CreateOrder -> service:sld', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key com.sap.engine.services.deploy.container.DeploymentException: <Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='Implied start failed for dependency :local/CreateOrder -> service:sld', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key Implied start failed for dependency :local/CreateOrder -> service:sld (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)

Hi Michael,
one way is to enhance the server go.bat with debug parameters. Under c:\usr\sap\<SID>\j2ee\<INSTANCE>\cluster\server\go.bat define the following params
set DEBUG_PORT=5000
set DEBUG_PARAMS=-Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=
and add both params to the java arguments (e.g. behind the -classpath): %DEBUG_PARAMS%%DEBUG_PORT%.
Regards,
Stefan

Debug mode for WD app in CE 7.1 EHP1

Hi experts,
I need to debug a WebDynpro application that I have created in my CE7.1 EHP1 environment.
In the config tool for the Java instance, I have set "Debug Mode" to true and checked the "Enable Debug node" checkbox.
I restarted the server after this and in SAP MMC Snap In, found that the server0 is running and the Debug column also shows a stauts of Switched on(<<port number>>)
When I try to create a new Debug Configuration using the Debug Dialog in NWDS, I select SAP Application and attach the appropriate WD app to the configuration.
At this point, the server instance is automatically selected, but I get the following error message:
Runtime: No debuggable node available. Open a debug session in SAP Management Console first
What might I be missing?
Regards,
Puja

Hi guys,
about one year later I had the same problem as Puja Malhotra.
Gopala Krishna gave the correct answer but unfortunately he missed to offer the suitable help. So I will catch up
You have to set the values "debuggable", "debug mode" and "debug port" with the Config Tool to edit the JVM Settings for a Specific Instance.
Have a look at:
[http://help.sap.com/saphelp_nwce71/helpdata/en/39/7796e0a7be604ab63c2924045710a8/content.htm]
After restart it should work!
Best regards

Reg: Debug mode

Hi,
How will i know that my application is running in debug mode and how to come out of that. I want to run the application in normal webdynpro mode.
Regards,
Subbareddy.

Hi,
Terminate debugging:
1. In the Debug View, call the context menu for the top node
2. In the context menu that appears, choose Disconnect.
Refer to the following link for debugging:
http://help.sap.com/saphelp_nw04/helpdata/en/c0/ef07876f9ef0479194965520f87837/frameset.htm

Debugging in Webdynpro java?

Hi All..
Can anybody explain in detail abt Debugging in Webdynpro java.(also send some documents and pdfs regarding tht)..
GS

Hi,
To debug an application
Run-> Debug->Webdynpr->
Right click and select new
Once this is done you will see four tabs
1)Debug: select your project and the application to launch
2) Select the SAP System for Debugging
3)Source need to be added here.
Enabling Debug mode is mentioned in the following docs
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/907751e5-f717-2a10-f3b4-de4431d4722d
http://help.sap.com/saphelp_nw04s/helpdata/en/66/547f09281d464b951c9a3a6b06a12d/frameset.htm
Regards
Ayyapparaj

How to determine if the server is in debug mode or Running in Java Code

Hi ,
I have a WebDynpro Applcation in which i have to display foll things in Table:
Engine Name; Engine Version: Debug Mode; Reserved by;
Now i could display list of servers but i have hardcoded the Debug Mode as "Disabled"
My Question is:
If i know the Server, can we find if the server is in debugmode in application code???
I have OS access to my Engine. Pls let me in which property file can i find Debug Status??
Also i am not sure if i have posted the Query in RIght Component. DO let e know if this Q is posted in wrong Forum
Kindly help me solve this problem
Thanks n Regards,
Archana

Hi Archana,
If u can't start the server in debugging mode thru NWDS then u can try this
Config Tool:
U can enable the debuggine mode from the Config Tool as well. Just browse to following
C:usrsap<SID>JC<SYS_NO>j2eeconfigtoolconfigtool.bat
Click on the your instance. Then under the tab VM Environment, Set the DebugMode = true.
Restart the engine now. This will open the J2EE server again in the Debug Mode.
Please check the [Debugging Portal Applications or WebDynpro Applciation|http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/907751e5-f717-2a10-f3b4-de4431d4722d?quicklink=index&overridelayout=true] and search for SDN
Just hope this helps you!
Regards
Vijay

Regarding Exception in Debug mode.

Hi All,
when i am starting Debugger,
it is giving an error like:-
Exception occured during creating launch configuration tabd.
reason:-No tab group define for launch configuration type com.sap.ide.webdynpro.projecrbrowser..launch.configtype.debug
Any idea?
how to correct it?

Hi, 
Did you check in your plug ins first if that com.sap.ide.webdynpro.projecrbrowser is avail or not. 
how to check this? 
Otherwise in technically server mode should be in debug mode and launch your application in debug mode I Mean to say go run-debug-create new web dynpro application and select your project and webdynpro application and checked the create and deploy the archive and click on run then it will wok 
The server mode is ON. While launching my application in debug mode, i am getting this message. it won't allow to create or edit configuration

How to debug the webdynpro application

Hi ,
i am facing a problem for debugging web dynpro application from offshore (my server is located in onsite) and i connected using VPN and also i changed my SDM Debug Mode to ON and also enable debugging of process also but it is giving error message like this
Failed to Connect to remote VM.Connection Refused

Hi Nageswara
The link provided shows you hoe to debug WebDynpro application.
Its a eLearning course available on sdn, which shows step by step process.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/media/uuid/3178ae74-0701-0010-ba8d-e3ca9f1edc1e
Hope ur problem is solved.
Pls award points for answers.

Debugging the webdynpro application

hi
    iam trying to debug my webdynpro application
      its showing as
      selected server node doesnot run in a restricted load
     balancing mode
         any suggestions ?

hi
thanks for the reply
i have gone through this document
in selecting the j2ee engine where we select
server node its showing up the error as in the cluster
we have two nodes server 0 and server 1
         any suggestions ?

ESS in debugging mode

Hi All,
When an employee logs in to ESS portal, need to know how this logging on takes place in the background (ABAP code, FM etc). Need to know what FMs/BAPIs are called right from the first step where it checks the userid info in infotype 0105.
In other words, the need is to see in debugging mode while the employee logs on.
Need to know what FMs are used and where to put the breakpoints etc.
Any help will be highly appreciated.
Thanks,
Mark.

Wow! You're really asking for it eh? haha You actually will have lots going on and not sure a trace will help you make sense of it all. Just from a high-level...
(1) login into portal => userid/pword are authenticated against whatever the portal uses as a source (ldap server, portal db, R3/ system, etc). If it passes this authentication, the portal then locates the user in it's own db to find what PORTAL roles to assign to build out the user's portal specific to them.
(2) Assuming single sign-on is set up, the portal issues a SAP Logonticket that is passed to the backend systems. This Logonticket is just a fancy non-persistent, encrypted cookie that contains (a) the userid (b) the portal's "key".
(3) when the user (via the portal) makes a request to the backend system, the portal "hands" the Logonticket to the other system. The other system checks the "key" and says "ok, yep this is the portal...I trust the portal...no need to check the userfurther such as password". The backend system then will take the userid (again, no password needed) and check that that userid actually exists. Let's assume it does. As with the portal, the backend system can now determine what security authorizations and roles (don't confuse with a portal role!) the user has.
(4) Now...that gets us to the "login" part of the backend. In the case of your ESS needs, we now could be playing with any number of possibilities.
   -ITS service which in turn is really running a SAP transaction (most common for ESS)
   -Webdynpro which is a Java app that calls SAP via BAPIs/RFCs
   -direct GUI access (via SAP WINGUI launched from portal)
   -other (custom apps that call RFCs/BAPIs)
   With all of the above there is usually some code in there that right off the bat will take the userid and try to find what employee it matches. Userid (ie. a system user record) is linked to employee records via infotype (kind of a HR table) 0105 (communication), subtype 0001 (SAP Userid). Given the current date, it will try to find which employee record has this userid assigned to IT0105 ST0001 (lots/most of HR records are date driven). If no employee record is found for the userid, you typically get an error that states something to the effect of "this userid does not match an employee record for this period".
From this point, all of the "what's going on" largely depends on what ESS service you are trying to perform (address change, benefits enrollment, etc).
Hope this helps.

NWDS debug mode can only be supported by one client ?

Hi all.
We are 4 persons who are developing webdynpro application together.
However, when we are using NWDS debug mode, we found that only one client debug is supported, when the second person want to debug, the first person have to exit debug mode.
Can WAS support for more debug mode ?

Hi Jianhong,
Right now you have only one instance of your server,so only one debug port is available.Hence only one person at a time can debug.
If you need to debug in development environment with more people then you have to create as many instance of server as you need.
Recently i have seen some forum/webblog here about it.

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

Debug Mode -WebDynpro

Similar Messages

Maybe you are looking for