Downsides to leaving J2EE in Debug Mode?

Hi All,
Are there any downsides to leaving j2ee in debug mode? Performance, etc? I'm only talking about Development.
Thanks,
Doug

We have had our dev server in debug mode for several months and have experienced no issues. We do reboot the dev server every weekend, but have been doing this even before the dev server was switched to debug mode.

Similar Messages

J2ee server doesn't started in debug mode

Hi.
I set J2EE server debug mode using configtool and I try to start J2EE.
At that time, dispatcher, SDM process started successfully but server process doesn't start.
SAP MMC has "waiiting for start" status for server process.
Any ideas ?
Regards, Arnold.

Right aside the Enable Debugging checkbox in the configtool, there's a 'Restricted Load Balancing' checkbox. As I remember, in some version of the J2EE engine, you need to invert its state in order to get debugging to run.
Regards,
Armin

How can I start local J2EE Engine in debug mode automatically?

Hello,
I thought there was a way to setup the local J2EE engine to automatically start in debug mode.
Right now, I have to start the engine, go into Studio and right-click on engine and choose "Enable debugging of process". This means that I have to wait for the engine to restart.
What I'm looking for is a system setting where I can tell it to automatically start in debug mode.
Thanks in advance for any help.
David.

Ivaylo,
Thanks for the quick reply.
Could you please elaborate on your instructions? I have started the Config Tool. Now I see the following tree structure:
+ cluster-data
   secure store
   UME LDAP data
I expand the cluster-data node and get this:
- cluster-data
    +Global dispatcher configuration
    +Global server configuration
    +instance_ID12345
Assumed that I should expand the instance node. When I do I get this:
    + dispatcher_ID1234500
    + server_ID123450
Again, I assumed I should expand the server node. This is where I get lost. I have no idea where to go next to set the debug configuration.
Can you please help?
Thanks
David.

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:
Property "Productive Use" of server0 has a value "YES".
 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

Debug mode of j2ee Process table??

Hello All,
In j2ee Process Table,3 processes are running.
SDM-Debug(Switched off)--SDM Server
Dispatcher-Disable---J2ee Dispatcher
Server0-Swiched off ---J2ee server
Why SDM server & server0 are swiched off & dispacher is disabled in the Debug mode??When we need to enable it??

Hi,
Refer these links.
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/558e9ae5-0601-0010-40a0-a1d35a13047d?overridelayout=true
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/3a83c242-0801-0010-dc95-d496cf6dba9d?overridelayout=true
let us know if u have any issues,
Regards,
Ravi

Enabling debug mode for j2ee engine

hi,
I would like to enable the debug mode for my j2ee engine (installed on a remote host)
I followed already the below mentioned steps, but I was not successfull
http://help.sap.com/saphelp_nw04/helpdata/en/ae/40e1407e858031e10000000a1550b0/content.htm
In the NWDS I see always that the Productive Use is enabled (YES). How can I switch this field to NO?
kind regards
Michael

Here the steps...
1.     login to config tool
2.     access serverX node
3.     select debug manu
4.     select all 3 option(checkbox)
                  "DebugMode" -> "yes"
                  "DebugPort" -> "50021"
                  "Debuggable" -> "yes"
5.              restart engine.

Error starting J2EE server in debug mode

I am trying to start the Sun 1.4 application server in a debug mode. I get an error
err:FATAL ERROR in native method: No transports initialized
: No such file or directory
Error [2] in bind() call!
Socket transport failed to init.
Transport dt_socket failed to initialize, rc = -1.
The setting in config.xml file is:-
debug-enabled="true" debug-options="-Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=1044
Any help will be appreciated.
Thanks,
Milind

I changed the port number and it worked. Not sure why port 1044 as specified in the Sun documentation doesnot work.
Milind

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

Starting Server in Debug Mode - Need Some Advice Plz.

Hi Guys,
I have an EP SP 12 Server Running and I am trying to Start the Server in Debug mode from the Netweaver Developer Studio but when I right click the Server and try to choose Debug, the option is greyed out and even while viewing the Debug option from the SAPMMC I see that under the column Debug, it say 'Disabled' for the Server and Dispatcher.
Can anyone suggest how this can be done, I would appreciate any help as I have been working on this for some time.
Best Wishes,
John.
Message was edited by: John Bray
Message was edited by: John Bray

Hi John,
If the you cannot start the server in the debugging mode through the NWDS then you can try the other way round.
Through Config Tool:
You can enable the debuggine mode from the Config Tool as well. Just visit the following path :
C:\usr\sap\<SID>\JC<SYS_NO>\j2ee\configtool\configtool.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.
I hope this helps you!!
Regards
Pravesh
PS: Please conside rewarding points if helpful and solved.

Error C3561: tile barrier operation...occurring in debug mode only

Hi,
I am new in C++ AMP, please, help me figure out why my code compile in Release mode, but C3561 occurring in debug mode.
At first, short version to demonstrate compile errors
parallel_for_each(D.extent.tile<TILE_SIZE>(), [=](concurrency::tiled_index<TILE_SIZE> t_idx) restrict(amp)
float threshold = P[t_idx.global];
tile_static float my_tile[TILE_SIZE];
tile_static int calculatedCount;
for (int stride=0; calculatedCount < TILE_SIZE; stride++)
my_tile[t_idx.local[0]] = P[t_idx.global[0] + stride*TILE_SIZE];
t_idx.barrier.wait();
for (int i =0; i < TILE_SIZE; i++)
if (my_tile[i] >= threshold)
D[t_idx.global] = 0;
calculatedCount++;
Short version does not compile in debug and release mode. Occurring very strange "tile barrier error" C3561.
However, full version shows more interesting results: compile errors only in debug mode,
parallel_for_each(D.extent.tile<TILE_SIZE>(), [=](concurrency::tiled_index<TILE_SIZE> t_idx) restrict(amp)
float threshold = P[t_idx.global] + tp;
float maxDrawdown = 0;
float open = P[t_idx.global];
tile_static float my_tile[TILE_SIZE];
tile_static int calculatedCount;
int stride = 0;
bool calculated = false;
calculatedCount = 0;
t_idx.barrier.wait();
for (; calculatedCount < TILE_SIZE; stride++)
if (t_idx.global[0] + stride*TILE_SIZE < sz)
my_tile[t_idx.local[0]] = P[t_idx.global + stride*TILE_SIZE];
t_idx.barrier.wait();
if (calculated)
continue;
for (int i = stride == 0 ? t_idx.local[0] : 0; i < TILE_SIZE; i++)
if (maxDrawdown < open - my_tile[i])
maxDrawdown = open - my_tile[i];
if (my_tile[i] >= threshold)
duration[t_idx.global] = stride*TILE_SIZE + i - t_idx.local[0];
D[t_idx.global] = maxDrawdown;
calculated = true;
calculatedCount++;
break;
if (stride*TILE_SIZE + i >= sz)
calculated = true;
calculatedCount++;
D[t_idx.global] = maxDrawdown;
duration[t_idx.global] = 0;
break;

Hello, thank you for your inquiry. The issue here is that you have a race condition and control flow that is conditional on the variable that's subject to the race. To be precise, in the simplified example, the following:
calculatedCount++;
has the effect that every lane tries to increment calculatedCount. Since there are no guarantees about ordering or completion with the given code, the compiler (reasonably) fears that this might result in a case where some lanes break out of the loop while
others do not (different calculatedCount values per lane). This is invalid due to the fact that the body of the loop contains a barrier (all lanes must see a barrier i.e. control flow must not diverge around it). Hence the odd error. The solution here
could be to use an atomic increment on calculatedCount and add a barrier after the innermost loop, so that the outermost loop is tile-synchronous, like so:
for (int stride=0; calculatedCount < TILE_SIZE; stride++) {
my_tile[t_idx.local[0]] = P[t_idx.global[0] + stride*TILE_SIZE];
t_idx.barrier.wait();
for (int i =0; i < TILE_SIZE; i++) {
if (my_tile[i] >= threshold) {
D[t_idx.global] = 0;
concurrency::atomic_fetch_inc(&calculatedCount);
t_idx.barrier.wait();
Also, as a curiosity, what is the intent of the innermost loop? My reading of it suggests that it is in error i.e. each value that you cache ends up being processed multiple times: all lanes process [0], then [1], then [2] etc. If [0] is above the threshold,
this means that you end the loop after processing just that one datum. Since I presume you want to process the data in my_tile, the way to achieve that is to remove the for and leave the body modified like so:
for (int stride=0; calculatedCount < TILE_SIZE; stride++) {
my_tile[t_idx.local[0]] = P[t_idx.global[0] + stride*TILE_SIZE];
t_idx.barrier.wait();
if (my_tile[i] >= threshold) {
D[t_idx.global] = 0;
concurrency::atomic_fetch_inc(&calculatedCount);
t_idx.barrier.wait();
Hope this helps! Cheers!

How to start server in debug mode by default

Hi,
Whenever the server starts it does not start in debug mode.
One has to manually start the "SDM" and "Server0" in the debug mode.
Is there a way I can make the server start in debug mode for the first time itself.
regards,
Saurabh

Hi Saurabh,
You can start the server in debug mode using config tool. Just open cofig tool (/usr/sap/<SYS ID>/JC<SYS NR>/j2ee/configtool/configtool.bat).
Click on the your instance. Then under the tab Servers Debug check Debuggable and also Enable Debug mode.
Restart the engine now.
However a word of caution: Starting the server in debug mode decreases the system performance. You should only start the dev server in debug mode.
Hope this helps.
Regards
Sidharth

Deployment problem in debug mode

Hi,
I developed a project in XP and moved to a laptop with vista. I am able to run (except *.exe) all files but I am not able run debug mode. I get the error:
Deploying application in domain failed; could not rename C:\program files\sun\creator2_1\sunappserver8\domains\creator\generated\xml\j2ee-modules\PAIRS5_
Log Level:     SEVERE
Logger:     javax.enterprise.system.tools.deployment
Name-Value Pairs:     _ThreadID=13;
Record Number:     2093
Message ID:     Exception occured in J2EEC Phase com.sun.enterprise.deployment.backend.IASDeploymentException
Complete Message
Could not rename C:\Program Files\Sun\Creator2_1\SunAppServer8\domains\creator\generated\jsp\j2ee-modules\PAIRS5 to C:\Program Files\Sun\Creator2_1\SunAppServer8\domains\creator\generated\jsp\j2ee-modules\PAIRS5_old
     at com.sun.enterprise.deployment.backend.ModuleDeployer.setOldDirs(ModuleDeployer.java:764)
     at com.sun.enterprise.deployment.backend.WebModuleDeployer.preRedeploy(WebModuleDeployer.java:241)
     at com.sun.enterprise.deployment.backend.ModuleDeployer.doRequestFinish(ModuleDeployer.java:158)
     at com.sun.enterprise.deployment.phasing.J2EECPhase.runPhase(J2EECPhase.java:148)
     at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:71)
     at com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhases(PEDeploymentService.java:639)
     at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:188)
     at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:520)
     at com.sun.enterprise.management.deploy.DeployThread.deploy(DeployThread.java:139)
     at com.sun.enterprise.management.deploy.DeployThread.run(DeployThread.java:168)
Is there any error I can fix??? Please help...
dr.am.mohan rao

Were you able to fix this? I am having the same issue.

DEBUG MODE

Is it possible to run the sneak preview SAP Web As to run in the debug mode. I am using NWDS to develop web dynpro applications. I am trying to debug.I went to Windows-> Show View->J2EE Engine. after selecting Server0, i right clicked to get the options to enable the debug option but all of them greyed out.
Thanks,
Sujatha

Hello Sujatha,
Yes it is possible to debug in the preview edition. First you have to make the engine debuggable and assign it a port. To do this you have to perform the following steps
1. Open the configtool by running the configtool.bat under your C:\usr\sap\J2E\JC00\j2ee\configtool directory.
2. Once the window opens up expand the instance_IDxxx node and click on server. On the right hand panel go to the debug tab
3. make sure the debuggable check box is checked and a free port is assigned (by default it is 50021).
4. Restart the server and the options should now be available.
Regards
Abdul

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

J2EE Engine Debugging ... Help required

There is a problem with the debugging my J2EE applications. I am a new user on SAP Portals. I set the server parameters through the config tool for setting the debugging of the server. But when I opened the Netweaver, it was still showing me the "Debug Mode Off". When i tried to set the problem from the preferences --> J2E Engine by selecting remote installation, it gave me the error "No server was defined under
sapmnt\.. Configure your server as Remote host"... I tried a lot but could not get through this problem.
I have a portal installation having a URL "http://kashruq:50000/". Earlier I had set the IP Address for my network card as 10.10.1.10 but later removed it and set the etc\hosts file accordingly. The J2EE server is running fine and the sample Car rental Application is also running fine, but I am unble to debug my J2EE applications, if I need to. Any body help me ?

Thanks Karsten
Actually I restarted the server from the Netweaver. But did not get the correct parameters for the debug mode. When I restarted the J2EE engine altogether then only I was able to see that the server0 is running with debug mode ON state. But still if I try to use the debug facility from the netweaver for the J2EE applications and try to set it from the Preferences\J2EE Engine then I still get the error.
The values I enter in the Preferences for the J2EE engine are:
server: kashruq (This is my machine name. so i connect to http://kashruq:50000/irj/portal ... etc.)
port: 3061 (default)
I set the debug mode through the config tool only. I can not set it from the netweaver, as it gives me error, as I mentioned in my first mail.
Any help?

Downsides to leaving J2EE in Debug Mode?

Similar Messages

Maybe you are looking for