[dlaskin]

I was able to step through my JSP code once, but now the breakpoints are ignored. Running Eclipse 2.1.2 and WebLogic 8.1 on XP. Any pointers appreciated!

[Scott Anderson]

Can you please post your full configuration information as we request in the ‘Posting Guidelines’ thread at the top of the forum? That, with a full description of exactly what you’re experiencing will enable us to help resolve the issue.

–Scott
MyEclipse Support

[dlaskin]

What operating system and version are you running?
WinXP Professional Ver 2002

What Eclipse version and build id are you using? (Help > About Eclipse Platform)
Version: 2.1.2
Build id: 200311030802

– Was Eclipse freshly installed for MyEclipse?
No.

– If not, was it upgraded to its current version using the update manager?
No.

– Are any other external plugins installed?
No.

– How many plugins in the <eclipse>/plugins directory are like org.eclipse.pde.*
10

What MyEclipse version are you using? (Help > About Eclipse Platform > Features)
2.6.4

What JDK version are you using to run Eclipse? (java -version)
1.4.2.02

What JDK version are you using to launch your application server?
1.4.2

What steps did you take that resulted in the issue?
I’m not sure. Have been tinkering with myEclipse and WebLogic 8.1, both of which are new to me.

What application server are you using?
WebLogic 8.1

Are there any errors in the Eclipse log? (<workspace>/.metadata/.log)

This looks relevant:

!ENTRY org.eclipse.jdt.debug 4 120 Dec 08, 2003 16:17:59.798
!MESSAGE Internal error logged from JDI Debug:
!STACK 0
com.sun.jdi.VMDisconnectedException: Got IOException from Virtual Machine
at org.eclipse.jdi.internal.connect.PacketSendManager.sendPacket(PacketSendManager.java:79)
at org.eclipse.jdi.internal.MirrorImpl.requestVM(MirrorImpl.java:169)
at org.eclipse.jdi.internal.MirrorImpl.requestVM(MirrorImpl.java:191)
at org.eclipse.jdi.internal.request.EventRequestImpl.enable(EventRequestImpl.java:222)
at org.eclipse.jdt.internal.debug.core.model.JDIDebugTarget.createClassPrepareRequest(JDIDebugTarget.java:960)
at org.eclipse.jdt.internal.debug.core.model.JDIDebugTarget.createClassPrepareRequest(JDIDebugTarget.java:927)
at com.genuitec.eclipse.wdt.jsp.debug.breakpoints.JSPLineBreakpoint.addToTarget(Unknown Source)
at org.eclipse.jdt.internal.debug.core.model.JDIDebugTarget.breakpointAdded(JDIDebugTarget.java:1043)
at org.eclipse.debug.internal.core.BreakpointManager$BreakpointNotifier.run(BreakpointManager.java:756)
at org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.java:1006)
at org.eclipse.core.runtime.Platform.run(Platform.java:413)
at org.eclipse.debug.internal.core.BreakpointManager$BreakpointNotifier.notify(BreakpointManager.java:782)
at org.eclipse.debug.internal.core.BreakpointManager.fireUpdate(BreakpointManager.java:684)
at org.eclipse.debug.internal.core.BreakpointManager.addBreakpoints(BreakpointManager.java:423)
at org.eclipse.debug.internal.core.BreakpointManager.addBreakpoint(BreakpointManager.java:400)
at org.eclipse.jdt.internal.debug.core.breakpoints.JavaBreakpoint.register(JavaBreakpoint.java:177)
at org.eclipse.jdt.internal.debug.core.breakpoints.JavaPatternBreakpoint$1.run(JavaPatternBreakpoint.java:66)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1595)
at org.eclipse.jdt.internal.debug.core.breakpoints.JavaBreakpoint.run(JavaBreakpoint.java:745)
at org.eclipse.jdt.internal.debug.core.breakpoints.JavaPatternBreakpoint.<init>(JavaPatternBreakpoint.java:69)
at org.eclipse.jdt.internal.debug.core.breakpoints.JavaPatternBreakpoint.<init>(JavaPatternBreakpoint.java:50)
at com.genuitec.eclipse.wdt.jsp.debug.breakpoints.JSPLineBreakpoint.<init>(Unknown Source)
at com.genuitec.eclipse.wdt.jsp.debug.JSPDebugUtility.createJspLineBreakpoint(Unknown Source)
at com.genuitec.eclipse.wdt.jsp.debug.actions.ManageBreakpointRulerAction.Ä…(Unknown Source)
at com.genuitec.eclipse.wdt.jsp.debug.actions.ManageBreakpointRulerAction.run(Unknown Source)
at org.eclipse.ui.texteditor.AbstractRulerActionDelegate.run(AbstractRulerActionDelegate.java:98)
at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:251)
at org.eclipse.ui.internal.PluginAction.run(PluginAction.java:213)
at org.eclipse.ui.texteditor.AbstractTextEditor$4.triggerAction(AbstractTextEditor.java:1767)
at org.eclipse.ui.texteditor.AbstractTextEditor$4.mouseDoubleClick(AbstractTextEditor.java:1781)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:136)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:81)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:840)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2022)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1729)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1402)
at org.eclipse.ui.internal.Workbench.run(Workbench.java:1385)
at org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.java:858)
at org.eclipse.core.boot.BootLoader.run(BootLoader.java:461)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.core.launcher.Main.basicRun(Main.java:291)
at org.eclipse.core.launcher.Main.run(Main.java:747)
at org.eclipse.core.launcher.Main.main(Main.java:583)

[Scott Anderson]

From the log, it looks like you’re experiencing a problem when the Eclipse debugger interacts with the latest build of JDK 1.4.2. Problems of this sort have been reported both here and on the eclipse newsgroups. I’m not sure if this is a bug in Eclipse or the latest JDK build, but based on experience I’d assume the latter. In either case the workaround is to use the latest version of JDK 1.4.1 instead. Sorry for the inconvenience.

–Scott
MyEclipse Support

[dlaskin]

Now have java.runtime.version=1.4.1_05-b01 but still not stopping at JSP breakpoints. Sometimes seeing the following, but not every time it skips over a breakpoint.

!ENTRY org.eclipse.jdt.debug 4 5010 Dec 09, 2003 13:31:18.767
!MESSAGE com.sun.jdi.VMDisconnectedException: Got IOException from Virtual Machine occurred retrieving frame count.
!STACK 0
com.sun.jdi.VMDisconnectedException: Got IOException from Virtual Machine
at org.eclipse.jdi.internal.connect.PacketReceiveManager.getReply(PacketReceiveManager.java:145)
at org.eclipse.jdi.internal.connect.PacketReceiveManager.getReply(PacketReceiveManager.java:158)
at org.eclipse.jdi.internal.MirrorImpl.requestVM(MirrorImpl.java:173)
at org.eclipse.jdi.internal.MirrorImpl.requestVM(MirrorImpl.java:191)
at org.eclipse.jdi.internal.MirrorImpl.requestVM(MirrorImpl.java:206)
at org.eclipse.jdi.internal.ThreadReferenceImpl.frameCount(ThreadReferenceImpl.java:147)
at org.eclipse.jdt.internal.debug.core.model.JDIThread.getUnderlyingFrameCount(JDIThread.java:599)
at org.eclipse.jdt.internal.debug.core.model.JDIThread.createAllStackFrames(JDIThread.java:520)
at org.eclipse.jdt.internal.debug.core.model.JDIThread.computeStackFrames(JDIThread.java:396)
at org.eclipse.jdt.internal.debug.core.model.JDIThread.computeStackFrames(JDIThread.java:492)
at org.eclipse.jdt.internal.debug.core.model.JDIThread.getTopStackFrame(JDIThread.java:989)
at org.eclipse.jdt.internal.debug.ui.JavaDebugOptionsManager.getProblem(JavaDebugOptionsManager.java:624)
at org.eclipse.jdt.internal.debug.ui.JavaDebugOptionsManager.breakpointHit(JavaDebugOptionsManager.java:607)
at org.eclipse.jdt.internal.debug.core.JDIDebugPlugin$HitNotifier.run(JDIDebugPlugin.java:510)
at org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.java:1006)
at org.eclipse.core.runtime.Platform.run(Platform.java:413)
at org.eclipse.jdt.internal.debug.core.JDIDebugPlugin$HitNotifier.notifyHit(JDIDebugPlugin.java:528)
at org.eclipse.jdt.internal.debug.core.JDIDebugPlugin.fireBreakpointHit(JDIDebugPlugin.java:322)
at org.eclipse.jdt.internal.debug.core.model.JDIThread.handleSuspendForBreakpoint(JDIThread.java:1018)
at org.eclipse.jdt.internal.debug.core.breakpoints.JavaBreakpoint.suspend(JavaBreakpoint.java:307)
at org.eclipse.jdt.internal.debug.core.breakpoints.JavaExceptionBreakpoint.handleBreakpointEvent(JavaExceptionBreakpoint.java:292)
at org.eclipse.jdt.internal.debug.core.breakpoints.JavaBreakpoint.handleEvent(JavaBreakpoint.java:262)
at org.eclipse.jdt.internal.debug.core.EventDispatcher.dispatch(EventDispatcher.java:136)
at org.eclipse.jdt.internal.debug.core.EventDispatcher.run(EventDispatcher.java:214)
at java.lang.Thread.run(Unknown Source)

[Scott Anderson]

Are you using 1.4.1 to both launch Eclipse and for the server? Can you post your Eclipse enviornment entries as retrieved from Help > About Eclipse Platform > Configuration Details?

–Scott
MyEclipse Support

[dlaskin]

I can’t publish my config details, but the answer to your question is no, I’m still using 1.4.2 to run WL 8.1. Does that have to run under 1.4.1 as well? If you still need my config info, please give me your email address so can I respond offline.

[dlaskin]

Btw, I’m now running both Eclipse and WL under 1.4.1.06, and JSP breakpoints are still not working. Breakpoints are working in regular Java classes in the same WebApp project though. 🙁

[Scott Anderson]

Now that we’ve gotten the JDK issues resolved, let’s make sure the configuration is correct.
Did you set up your weblogic.xml file in your web project for debugging like this:

<!DOCTYPE weblogic-web-app PUBLIC "-//BEA
Systems, Inc.//DTD Web Application 7.0//EN"
"http://www.bea.com/servers/wls700/dtd/weblogic700-web-jar.dtd">
<weblogic-web-app>
    <description>WebLogic Descriptor</description>
    <jsp-descriptor>
        <jsp-param>
            <param-name>debug</param-name>
            <param-value>true</param-value>
        </jsp-param>
    </jsp-descriptor>
</weblogic-web-app>

Note the debug parameter you need to turn on. From your description, this is most likely the problem now.

–Scott
MyEclipse Support

[Author]

Posts