on 03-24-2006 12:39 PM
Hi,
I am trying to debug an application.
I have built the project and exported into a war file.
Later I uploaded it to Webconsole and deployed to the MI client.
I try to debug the application,the mi client is launched.
I login and try to access the application. As soon the break point that I have inserted becomes active
the application hangs. I am not able to use the functions Step into,Step over etc. Is there any problem in the way that I have built or is there something called building in debug mode.
Regards
Raja Sekhar
Hi Kishore
When I am building the application, I get an error that Obsolete methods on the stack.
The reason displayed is : Virtual machine was unable to remove all stack frames from the old code. The virtual machine is not supplying the debugger with valid data for those frames.
I dont know what this virtual machine is and how to remove the error. I guess that is the reason I am unable to debug the app. Please let me know as to how I can increase the vm size
Regards
Raja Sekhar
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Raja,
have u created a new application or migrated that one developed in SP 9 into this version of studio?.
In the virtual parameters part give this.
-Xms384m -Xmx384m -XX:NewSize=128m -XX:MaxNewSize=128m
and refer this also ..
http://java.sun.com/docs/hotspot/PerformanceFAQ.html
U have to give..
"-home:C:\Program Files\SAP Mobile Infrastructure" -trace -url:<Your application name>/start -app:jsp in the Program Arguments part.
try this. im not sure. we have not faced a situation like this.
Regards
Kishor Gopinathan
hello raja,
this problem is not specific to NWDS but this sometimes
occurs in Eclipse. try closing other projects and restarting
you IDE. try also editing the VM related parameters for NWDS
such as -Xmx512m and -Xms256m which is located in the
vm.parameters file in eclipse folder of your JDT installation.
when your eclipse does not update your debug threads, try
refreshing your debug view by switching to java perspective
then again back to debug perspective. or try pressing F5
once...
regards
jo
Hi Raja,
it might be bcoz of the lack of memory available in your system. i think so.
hope u have followed this blog.
/people/arunkumar.ravi/blog/2006/02/22/execute-debug-your-mi-code-from-nwds
i have one suggestion , just close other applications , that u r currently running. increase the VM size of your system..
then put proper VM parameters in teh Arguments tab of Debug window..
refer
http://www.caucho.com/resin-3.0/performance/jvm-tuning.xtp .. im not sure...
Regards
Kishor Gopinathan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
83 | |
10 | |
10 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.