- This topic has 7 replies, 2 voices, and was last updated 16 years, 11 months ago by
.
-
Posts
-
I am using weblogic 8.1, Myeclipse 4.1.1 GA. I am debugging an application ear file deployed in weblogic 8.1 server. I am able to do remote debugging but when I am trying to display the variables in expression dialog box, it says
<variableName> can not be resolved.
I am using expired version of MyEclipse though. My team has no problem to buy if this issue is can be resolved because it is hurting us badly.
compuware,
A few things to check:1. You are sure that you have scope in order to see the evaluated value of the variable you are debugging?
2. Are you debugging a JSP or a Class file where the variable exists?
3. If you mouse over the value in the editor near the breakpoint, can you see iit’s value?
4. Are you sure that the current line of execution is *after* the line that instantiates the value you are trying to evaluate?
5. Are you able to reproduce this, using Tomcat, with any of the projects from the Examples on Demand repository? The reason I ask is because if we can narrow this down to a test case that both you and I can walk through, I can get this fixed faster. Since I don’t have access to your project, I figured we can try and reproduce this on Tomcat with one of the example projects faster.
I tried a few example projects, and they were all displaying the variables and evaluating expressions correctly… but maybe it’s possible I missed a detail from your scenario?
I am debugging a java class deployed in an ear file in weblogic server. Yes I am debugging java class not jsp. ear file is built using ant build.
From eclipse, I am able to connect to remote jvm and debug. Only variables are not getting displayed. When I take the mouse on variables,
it shows nothing. The scope of variable should not have any issue. It is fine.When I did unit testing of the same class deployed as a jar, ( the jar was exploded one compiled from my eclipse), i did niot face any issue.
I am facing the issue when I am debugging the class inside the entire application (ear). Also this time, ear was built from command line using ant.I see, you hadn’t mentioned Ant before. In that case it might be an issue with how Ant is building the EAR. Can you double-check the build targets inside the Ant script to make sure the <javac> task is setting the debug property to true and the debuglevel to all 3 proper settings to make sure all the sufficient debugging information is contained in them?
Thanks, it works. I only did the settings DEBUG=TRUE and it works for me. I need not to any debug level settings. Thanks again. Also can u pls write one or two lines regarding debug level settings.
I’m glad that worked. The debuglevel attribute has 3 arguments you can set: lines, vars, and source
So it would look like: debuglevel=”lines,vars,source”
More information here: http://ant.apache.org/manual/CoreTasks/javac.html
