| Author |
Message |
|
|
Post subject: Debugging isn't working with Oracle 10g and MyEclipse 7.0
Posted: Jan 05, 2009 - 10:58 PM
|
|
Registered Member


Joined: Oct 03, 2008
Posts: 19
|
|
I just switched to MyEclipse 7.0 (from 6.5). I moved my applicaitons over and when I deployed an enterpirse app to the 10g server the breakpoints don't work as they did previously. Is there something else I should do or know about 7.0? |
|
|
| |
|
|
|
 |
|
|
Post subject: RE: Debugging isn
Posted: Jan 06, 2009 - 06:51 PM
|
|
Registered Member


Joined: Apr 18, 2007
Posts: 8012
|
|
Can you go to MyEclipse > Installation Summary > Installation Details and paste the infomration here for me.
If you create a new project and try debugging it, do the break points work? |
_________________ Nipun
MyEclipse Support
|
| |
|
|
|
 |
|
|
Post subject: RE: Debugging isn
Posted: Jan 06, 2009 - 10:38 PM
|
|
Registered Member


Joined: Oct 03, 2008
Posts: 19
|
|
Here's the install info:
*** Date:
Tuesday, January 6, 2009 3:35:51 PM MST
** System properties:
OS=WindowsXP
OS version=5.1.0
Java version=1.5.0_11
*** MyEclipse details:
MyEclipse Enterprise Workbench
Version: 7.0
Build id: 7.0-20081201
*** Eclipse details:
MyEclipse Enterprise Workbench
Version: 7.0
Build id: 7.0-20081201
Eclipse Platform
Version: 3.4.1.r341_v20080731-9I96EiDElYevwz-p1bP5z-NlAaP7vtX6Utotqsu
Build id: M20080911-1700
Eclipse Java Development Tools
Version: 3.4.1.r341_v20080709-0800-7o7tEAfEF_U5qyUgrb2HAp539P97
Build id: M20080709-0800
Eclipse Graphical Editing Framework GEF
Version: 3.4.1.v20080806-67718083A56B4H2A3213573
Build id: 200809101400
Eclipse RCP
Version: 3.4.100.r341_v20080814-989JESIEdAciFYfkZZsBfSwQ2341
Build id: M20080703-0800
Eclipse Plug-in Development Environment
Version: 3.4.1.r341_v20080731-7T7U0E9mlRIuGUYviF_VP
Build id: M20080703-0800
Eclipse startup command=-os
win32
-ws
win32
-arch
x86
-showsplash
-launcher
C:\Program Files\Genuitec\MyEclipse 7.0\myeclipse.exe
-name
Myeclipse
--launcher.library
C:\Program Files\Genuitec\MyEclipse 7.0\../Common\plugins\org.eclipse.equinox.launcher.win32.win32.x86_1.0.101.R34x_v20080731\eclipse_1115.dll
-startup
C:\Program Files\Genuitec\MyEclipse 7.0\../Common\plugins\org.eclipse.equinox.launcher_1.0.101.R34x_v20080819.jar
-clean
-configuration
C:\Program Files\Genuitec\MyEclipse 7.0\configuration
-vm
C:\Program Files\Genuitec\Common\binary\com.sun.java.jre.win32.x86_1.5.0.011\bin\client\jvm.dll
Also, I veiwed the error log. There are quite a few entries. Here's the last one for example.
!ENTRY org.eclipse.ui 4 0 2009-01-06 15:25:15.062
!MESSAGE Unhandled event loop exception
!STACK 0
org.eclipse.swt.SWTException: Failed to execute runnable (org.eclipse.swt.SWTException: Widget is disposed)
at org.eclipse.swt.SWT.error(SWT.java:3777)
at org.eclipse.swt.SWT.error(SWT.java:3695)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3800)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3425)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2382)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2346)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2198)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:493)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:288)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:488)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:193)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:386)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
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.equinox.launcher.Main.invokeFramework(Main.java:549)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
at org.eclipse.equinox.launcher.Main.run(Main.java:1236)
Caused by: org.eclipse.swt.SWTException: Widget is disposed
at org.eclipse.swt.SWT.error(SWT.java:3777)
at org.eclipse.swt.SWT.error(SWT.java:3695)
at org.eclipse.swt.SWT.error(SWT.java:3666)
at org.eclipse.swt.widgets.Widget.error(Widget.java:463)
at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:336)
at org.eclipse.swt.widgets.Table.getItems(Table.java:2399)
at org.eclipse.jface.viewers.CheckboxTableViewer.preservingSelection(CheckboxTableViewer.java:279)
at org.eclipse.jface.viewers.StructuredViewer.refresh(StructuredViewer.java:1455)
at org.eclipse.jface.viewers.ColumnViewer.refresh(ColumnViewer.java:548)
at org.eclipse.jface.viewers.StructuredViewer.refresh(StructuredViewer.java:1412)
at com.genuitec.eclipse.ast.deploy.core.ui.dialog.DeploymentManagerDialog$7.run(Unknown Source)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:133)
... 22 more
Does this mean anything important?
thanks |
|
|
| |
|
|
|
 |
|
|
Post subject: RE: Debugging isn
Posted: Jan 07, 2009 - 03:45 PM
|
|
Registered Member


Joined: Apr 18, 2007
Posts: 8012
|
|
Did you try debugging a new project. Did you run into the same issue ? |
_________________ Nipun
MyEclipse Support
|
| |
|
|
|
 |
|
|
Post subject: RE: Debugging isn
Posted: Jan 07, 2009 - 11:01 PM
|
|
Registered Member


Joined: Oct 03, 2008
Posts: 19
|
|
Ok, I'v uninstalled all of MyEclipse and cleaned up the registry then re-installed MyEclipse 7.0
I've created a very simple web project and it's associated enterprise project.
I put a simple println statement in the index.jsp.
I deployed the application, set a breapoint on the println statement and MyEclipse ignored it (the same results a before).
Here's the console output when deploying:
09/01/07 15:53:45 Notification ==> Application UnDeployer for TestEnt COMPLETES [ Wed Jan 07 15:53:45 MST 2009 ]
09/01/07 15:59:36 Auto-unpacking D:\Oracle\oc4j\j2ee\home\application-autodeploy\TestEnt.ear... done.
09/01/07 15:59:36 Auto-unpacking D:\Oracle\oc4j\j2ee\home\application-autodeploy\TestEnt\TestWeb.war... done.
09/01/07 15:59:36 Auto-deploying TestEnt (New server version detected)...
09/01/07 15:59:37 ApplicationServer: appName = HMMS_EntApp
09/01/07 15:59:37 Auto-deploying file:/D:/Oracle/oc4j/j2ee/home/application-autodeploy/TestEnt/TestWeb/ (New server version detected)...
09/01/07 15:59:37 Installed TestEnt...
09/01/07 15:59:37 Auto-binding web-app 'TestWeb' to web-site 'OC4J 10g (10.0.2) HTTP Web Site' at '/TestWeb'...
Here's a portion of the jsp code that I have:
<body>
This is my JSP page. <br>
<%
System.out.println("testline");
%>
</body>
My applicaiton debugged fined when using MyEclipse 6.5 and I haven't changed anything execpt MyEclipse
thanks,
Larry |
|
|
| |
|
|
|
 |
|
|
Post subject: RE: Debugging isn
Posted: Jan 08, 2009 - 10:18 PM
|
|
Registered Member

Joined: Jan 06, 2004
Posts: 23824
|
|
Larry,
There is something going on here, I'm filing a bug for us to investigate this. |
_________________ Riyad
MyEclipse Support
|
| |
|
|
|
 |
|
|
Post subject: RE: Debugging isn
Posted: Jan 08, 2009 - 11:48 PM
|
|
Registered Member


Joined: Oct 03, 2008
Posts: 19
|
|
What would the next steps be then?
thanks |
|
|
| |
|
|
|
 |
|
|
Post subject: RE: Debugging isn
Posted: Jan 09, 2009 - 04:34 PM
|
|
Registered Member


Joined: Oct 03, 2008
Posts: 19
|
|
I changed the compiler compliance to 1.4 from 1.3. This caused the debugger to give the "source not found" error that others are having.
Larry |
|
|
| |
|
|
|
 |
|
|
Post subject: RE: Debugging isn
Posted: Jan 12, 2009 - 08:53 PM
|
|
Registered Member

Joined: Jan 06, 2004
Posts: 23824
|
|
No next steps until the dev team gets time to investigate what is going on here. For some reason either the source map coming back from the app server is insufficient for the IDE to break at the correct location, or it's communicating incorrectly with the server's VM to get the information. |
_________________ Riyad
MyEclipse Support
|
| |
|
|
|
 |
|
|