[suraphol]

Hi,

I have a Windows XP Pro PC, running WorkBench 5.1.0GA (using all-in-one installation method).

I have WebLogic 9.2 running locally, and I have set up “Project->Properties->Java Build Path->Source” to include all my sources already, and included jars that I need. Also, I have set the “Compiler complianace level” to “5.0” because I am using the new annotations. I am also using JDK150_06 that comes with WebLogic 9.2 to start the app server.

I have compiled and deployed the EAR file in 9.2 already. I also have the app server running in debug mode. I ***used to be able*** (for this deployemnt) to step into the source (in the deployed EJBs) during debugging, but now I cannot. This occurrance sometimes happen (but I do not recall what might have caused it). I noticed that the logging (log4j) does not show up the line number (it used to). I can run the test client with no problem until end, and the logging is also done in the console and in the log4j log file, but I just cannot step into the EJB method.

Would you please give me a check list of what I should check again to see what is messed up in order to enable ‘step-into-code’ in debug mode again.

Thanks in advance…

[Scott Anderson]

What happens if you set a breakpoint in your EJB source code then execute that code? Is the breakpoint hit? Is the source shown?

[suraphol]

Hi Scott,

I can ‘set’ the breakpoint. But when I run my test client that calls the EJB, it just run ‘through’ the code (with logging to the console correctly), but it does not stop at the breakpoint. I used to be able to ‘step through’ into the EJB code.

My WebLogic 9.2 comes with JDK1.5.0_06, which I used to start it within the workbench. But workbench comes with a different version of JDK. I wonder if I need to compile the code with the workbench’s version and then debug it, but use the WebLogic’s version to bring up the app server?

Thanks…

[Riyad Kalla]

suraphol,
If your logging and debugging are not longer working correctly then my guess is that possibly the compilation arguments you selected for your project are no longer including the debugging information correctly in the class files.

Can you double-check your compiler settings for the project that they are overriding the workbench defaults and setting the debug information in the generated class files?

[suraphol]

Would you please point to me the place in project settings that I need to check the compiler setting for debugging? (I am not sure where to specify the settings that can override workbench’s default) Thanks…

[Riyad Kalla]

My appologies. Open up your project properties and you should see a screen similar to the below, note the areas I’ve highlighted.

Attachments:

You must be logged in to view attached files.

[suraphol]

I have found the problem. I need to include ‘debug=”true”‘ in my javac Ant task. Funny thing is, for the same project, when I run in WebLogic App Server 8.1, I don’t have this attribute set and I debug fine.

[Author]

Posts