[Tony]

Synopsis:

Previously I was using MyEclipse 4.1.1GA with Eclipse 3.1.2, and native JSP debugging worked well with WebSphere 6.0. Since upgrading to the latest tandem of Eclipse 3.2 and MyEclipse 5.0M2, the breakpoints that I set in a JSP are not properly registered with WebSphere: a checkmark no longer appears as part of the breakpoint symbol; the breakpoint in the JSP gets ignored. Breakpoints in Java code still work as normal. If I set a breakpoint in Java code that is called by a JSP and then step out of the suspended Java code back into the calling JSP, then I can step line-by-line through the JSP, but any breakpoints that are set in the JSP are still ignored.

I followed the posted installation instructions for upgrading to 5.0M2. Did I fail to do something to enable proper execution of native JSP debugging, or is the MyEclipse Websphere plug-in defective with the latest milestone release?

==================================================================

Requested Information:

*** Date: Wed Aug 02 14:35:20 EDT 2006

*** System properties:
OS=Windows2000
OS version=5.0
Java version=1.5.0_06

*** MyEclipse details:
MyEclipse Enterprise Workbench

Version: 5.0 Milestone 2
Build id: 20060703-5.0-M2

*** Eclipse details:
Eclipse SDK

Version: 3.2.0
Build id: M20060629-1905

Eclipse Platform

Version: 3.2.0.v20060609m-AgOexn6hlEUsvBO
Build id: M20060629-1905

Eclipse RCP

Version: 3.2.0.v20060609m-SVDNgVrNoh-MeGG
Build id: M20060629-1905

Eclipse Java Development Tools

Version: 3.2.0.v20060609m-F7snq1fxia-Z4XP
Build id: M20060629-1905

Eclipse Plug-in Development Environment

Version: 3.2.0.v20060609m——6zXJJzJzJq
Build id: M20060629-1905

Eclipse Project SDK

Version: 3.2.0.v20060609m-GNq6oQq-7es-Y81
Build id: M20060629-1905

Eclipse Graphical Editing Framework

Version: 3.2.0.v20060626
Build id: 20060627-0816

Eclipse startup command=-os
win32
-ws
win32
-arch
x86
-launcher
C:\eclipse\eclipse.exe
-name
Eclipse
-showsplash
600
-exitdata
b74_54
-vm
C:\WINNT\system32\javaw.exe

Eclipse was freshly installed for this version of MyEclipse. The following external plug-in is installed: oXygen XML Editor and XSLT Debugger v7.2.0

Directory of C:\eclipse\plugins

07/11/2006 09:24a <DIR> org.eclipse.pde.build_3.2.0.v20060603
06/29/2006 08:24p 772,717 org.eclipse.pde.core_3.2.0.v20060605.jar
06/29/2006 08:24p 3,000,152 org.eclipse.pde.doc.user_3.2.0.v20060605.jar
06/29/2006 08:24p 8,446 org.eclipse.pde.junit.runtime_3.2.0.v20060605.jar
06/29/2006 08:24p 135,378 org.eclipse.pde.runtime_3.2.0.v20060605.jar
07/11/2006 09:23a <DIR> org.eclipse.pde.source_3.2.0.v20060609m——6zXJJzJzJq
06/29/2006 08:24p 3,378,092 org.eclipse.pde.ui_3.2.0.v20060605.jar
5 File(s) 7,294,785 bytes
2 Dir(s) 4,641,140,736 bytes free

The application server being used is IBM WebSphere 6.0.

[Riyad Kalla]

First, thank you for the detailed issue reports.

Secondly, switch to your debug perspective, right click in the breakpoints view and select Remove All. Then try restarting using the -clean command line argument as outlneid here: http://www.myeclipseide.com/PNphpBB2+file-viewtopic-t-10280-sid-9edd7dfb5c7b5dc8f8a8dee640105719.html

Then try and run WebSphere then set a break point, does a check box show up? If not, let’s try a new workspace just for sanity sake:
1) File > Switch Workspace > C:\tempworkspace, hit OK
2) Create a simple Web Project or EAR project, depending on what WebSphere requires. Create a single index.jsp file usnig the default JSP template.
3) Reconfigure WebSphere 6
4) Deploy and install your project to WebSphere, make sure you can access that sample JSP
5) Click to set a breakpoint near the top of the page where the basepath is computed, does the checkbox appear?

[Tony]

Hello Riyad:

@support-rkalla wrote:

First, thank you for the detailed issue reports.

You’re perfectly welcome. 🙂

@support-rkalla wrote:

Secondly, switch to your debug perspective, right click in the breakpoints view and select Remove All. Then try restarting using the -clean command line argument as outlneid here: http://www.myeclipseide.com/PNphpBB2+file-viewtopic-t-10280-sid-9edd7dfb5c7b5dc8f8a8dee640105719.html

Then try and run WebSphere then set a break point, does a check box show up?

No, I’m afraid it does not. 🙁

@support-rkalla wrote:

… If not, let’s try a new workspace just for sanity sake:
1) File > Switch Workspace > C:\tempworkspace, hit OK
2) Create a simple Web Project or EAR project, depending on what WebSphere requires. Create a single index.jsp file usnig the default JSP template.
3) Reconfigure WebSphere 6
4) Deploy and install your project to WebSphere, make sure you can access that sample JSP
5) Click to set a breakpoint near the top of the page where the basepath is computed, does the checkbox appear?

The checkmark does not appear within the blue breakpoint symbol.

The breakpoint at line

String basePath = request.getScheme()+"://"+request.getServerName()+":"+request.getServerPort()+path+"/";

in the test JSP gets ignored.

As another test, I added a test class and placed a breakpoint within its test method. The checkmark does appear within the blue breakpoint symbol, and the breakpoint does get honored.

Summary:

[1] I followed the steps above which included running eclipse with “-clear” option, creating a new workspace, creating a test J2EE project and configuring it with Websphere.

[2] Breakpoints created within the default JSP file have no checkmark within the breakpoint symbol and are ignored; breakpoints within the Java file do have the checkmark within the breakpoint symbol and get honored by the App server.

What do you suggest I try next?

[Riyad Kalla]

Are you building and deploying the project completely from MyEclipse or are you using a custom Ant script at any point?

Also are you launching Websphere from within MyEclipse?

If you navigate to your WebSphere 6 connector settings under Launch, si it set to launch in Run or Debug mode?

Lastly, if you launch WebSphere externally, then use our remote debugging feature to connect, does debugging work then? (guide: http://www.myeclipseide.com/images/tutorials/quickstarts/remotedebugging/ )

[Tony]

@support-rkalla wrote:

Are you building and deploying the project completely from MyEclipse or are you using a custom Ant script at any point?

I am deploying completely from MyEclipse.

@support-rkalla wrote:

Also are you launching Websphere from within MyEclipse?

Yes.

@support-rkalla wrote:

If you navigate to your WebSphere 6 connector settings under Launch, si it set to launch in Run or Debug mode?

It appears to be set to launch in “Debug” mode.

@support-rkalla wrote:

Lastly, if you launch WebSphere externally, then use our remote debugging feature to connect, does debugging work then? (guide: http://www.myeclipseide.com/images/tutorials/quickstarts/remotedebugging/ )

Ok, I followed the guide to setup remote debugging for the test project. I configured Websphere appropriately and restarted the server outside of MyEclipse. I set breakpoints in the test JSP page and inside a method in the test Java code. Same results as before: breakpoints are only honored in the Java code.

What should I try next?

[debedb]

Are you building and deploying the project completely from MyEclipse or are you using a custom Ant script at any point?

The application was exported as EAR from MyEclipse, installed via
WAS admin console. Then deployment was set up in MyEclipse.
The changes do get hot-deployed.

Also are you launching Websphere from within MyEclipse?

Yes.

If you navigate to your WebSphere 6 connector settings under Launch, si it set to launch in Run or Debug mode?

Debug mode.

Lastly, if you launch WebSphere externally, then use our remote debugging feature to connect, does debugging work then? (guide: http://www.myeclipseide.com/images/tutorials/quickstarts/remotedebugging/ )

Haven’t tried yet…

[Riyad Kalla]

Wait hold off on trying, I just had an email in my inbox from our issue tracker that a bug labelled “Debugging/Breakpoints not working in WebSphere”. The bug has been fixed and will be in the 5.0 GA release, I think that’s what is going on here. Sorry for the trouble.

[Tony]

@support-rkalla wrote:

Wait hold off on trying, I just had an email in my inbox from our issue tracker that a bug labelled “Debugging/Breakpoints not working in WebSphere”. The bug has been fixed and will be in the 5.0 GA release, I think that’s what is going on here. Sorry for the trouble.

Ah, so it is a known bug. That’s good to know that the fix for it will be included in the next release. Is the GA release still on track for early August (perhaps some time next week)? 😀

[Riyad Kalla]

Yes, 3 days actually.

[Tony]

@support-rkalla wrote:

The bug has been fixed and will be in the 5.0 GA release, I think that’s what is going on here. Sorry for the trouble.

I just downloaded and installed the 5.0GA release of MyEclipse. There seems to be an issue with the WebSphere JSP debugger fix. When I toggle a breakpoint in a JSP page, two identical breakpoints show up in the “Breakpoints” tab under the “JSP Breakpoints” branch. The first breakpoint of the pair is non-functional and should be deleted.

[Riyad Kalla]

Can you try this:
1) File > Switch Workspace > C:\tempworkspace, hit OK to restart
2) Reconfigure the WebSphere connector
3) Create a new web project, add 1 JSP to it called index.jsp and use the default JSP template
4) Launch and debug, does the double break point issue happen?

[Tony]

@support-rkalla wrote:

Can you try this:
1) File > Switch Workspace > C:\tempworkspace, hit OK to restart
2) Reconfigure the WebSphere connector
3) Create a new web project, add 1 JSP to it called index.jsp and use the default JSP template
4) Launch and debug, does the double break point issue happen?

I followed the above steps and two breakpoints are still getting created instead of one. The first breakpoint of the two appears to be useless.

[dbakerwes]

@tonedef wrote:

I followed the above steps and two breakpoints are still getting created instead of one. The first breakpoint of the two appears to be useless.

I’m seeing similar behavior with Tomcat 5.0, in relation to my other post:

http://myeclipseide.com/PNphpBB2+file-viewtopic-t-13763.html

Doug

[Riyad Kalla]

Guys I’m having a hard time reproducing the double break point issues on my end. Any tips for a clean install of Eclipse 3.2 GA and MyEclipse 5.0 GA with a clean workspace and either Tomcat 5.5 or WebSphere 6.0 or 6.1, on how to do it?

[dbakerwes]

@support-rkalla wrote:

Guys I’m having a hard time reproducing the double break point issues on my end. Any tips for a clean install of Eclipse 3.2 GA and MyEclipse 5.0 GA with a clean workspace and either Tomcat 5.5 or WebSphere 6.0 or 6.1, on how to do it?

Yep. In fact I can do it w/o any app server configured.

1. File.. Switch Workplace. Make a brand new workspace.
2. File.. New Project.
3. Web Project
4. Call it “test”, default location, default folder names, J2EE 1.4, JSTL unchecked
5. Finish, then Yes to open MyEclipse J2EE Development perspective
6. Right-click test in Package Explorer, New.. JSP (Advanced Template)
7. Default for all values.. Finish
8. Window..Open Perspective..Other..Debug
9. Right-click in MyJsp.jsp.. show line numbers
10. Highlight the breakpoints tab to show breakpoints. Right now it’s empty.
11. Right-click to add a breakpoint, anywhere. Several attempts to add a breakpoint do nothing, i.e. no breakpoints are added. Eventually (say on line 4) it will add a breakpoint, and now the Breakpoints window shows 2 breakpoints, both on line 4.

Note that I can only do this with JSPs. A breakpoint in a Java application pops up on the first try, and only one is listed. I wonder if this is also the cause of my JSP breakpoints being ignored, per my other post.

Doug

[Author]

Posts