[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [platform-debug-dev] Processor pegged at 100% and Editor unresponsive when I hit a break point
|
The help path for concrete problems such as this is through bugzilla, with
a reproduceable test case. As provided in my response is a link to a bug
that sounds similar, and has been addressed in 3.0.1:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=69536
Darin
John Marsi <mars58eclipse58@xxxxxxxxx>
Sent by: platform-debug-dev-admin@xxxxxxxxxxx
08/03/2004 10:29 AM
Please respond to
platform-debug-dev
To
platform-debug-dev@xxxxxxxxxxx
cc
Subject
Re: [platform-debug-dev] Processor pegged at 100% and Editor unresponsive
when I hit a break point
I apologize if this was the wrong place for this post. I wanted to gather
as much information as I could before running to a bug list. I was hoping
as the developers some one could tell me something about this issue or
point me in the right direction to do some further investigation.
This problem has plagued our current development efforts using WSAD and
Commerce ever since we switched from Commerce 5.4 to 5.5. 6 months ago.
The debugger allows me to step through my problems successfully maybe once
in five restarts which is very time consuming as you could well imagine.
There are people on our dev team that have stopped even trying to use the
debugger and have resorted to System outs and the like.
So I hope you can understand my frustration. I am looking for any help I
can get to resolve our issues and renew my faith and my developer’s faith
in WSAD and IBM Commerce.
I have actually gotten helpful responses from the Eclipse people here
before and was hoping to find the same. I guess my luck just ran out.
Darin Wright <Darin_Wright@xxxxxxxxxx> wrote:
This sort of problem should be posted as a bug or on the newsgroup, rather
than the developer mailing list.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=69536
Darin
John Marsi
Sent by: platform-debug-dev-admin@xxxxxxxxxxx
07/30/2004 11:52 AM
Please respond to
platform-debug-dev
To
platform-debug-dev@xxxxxxxxxxx
cc
Subject
[platform-debug-dev] Processor pegged at 100% and Editor unresponsive when
I hit a break point
Hello,
I am using
WebSphere Studio Application Developer (Windows) Version: 5.1.0 Build id:
20030726_2016
Running IBM WebSphere Commerce Server 55 Fix Pack 3
On windows 2000 Pro Version 5.0.2195 SP3 Build2195
It seems whenever I hit a break point my processor is pegged a 100% and
the edi tor is unresponsive. Sometimes it comes out of this other times I
have to kill the editor and restart.
Below are some exceptions that may apply.
Any help in this matter is greatly appreciated.
Thank You,
Jon
!SESSION Jul 30, 2004 11:17:40.656
---------------------------------------------java.fullversion=J2RE 1.3.1
IBM J9 build 20030702 (JIT enabled) BootLoader constants: OS=win32,
ARCH=x86, WS=win32, NL=en_US Command-line arguments: -os win32 -ws win32
-arch x86 -data C:\WebSphere\workspace_libdev -install
file:C:/WebSphere/Studio5/eclipse/
!ENTRY org.eclipse.jdt.debug 4 120 Jul 30, 2004 11:17:40.656
!MESSAGE Internal error logged from JDI Debug: !STACK 0
com.sun.jdi.VMDisconnectedException: Got IOException from Virtual Machine
at java.lang.Throwable.(Throwable.java)
at java.lang.Throwable.(Throwable.java)
at
com.sun.jdi.VMDisconnectedException.(VMDisconnectedException.java)
at
org.eclipse.jdi.internal.connect.PacketSendManager.sendPacket(PacketSendManager.java)
at org.eclipse.jdi.internal.MirrorImpl.requestVM(MirrorImpl.java)
at org.eclipse.jdi.internal.MirrorImpl.requestVM(MirrorImpl.java)
at org.eclipse.jdi.internal.MirrorImpl.requestVM(MirrorImpl.java)
at
org.eclipse.jdi.internal.ThreadReferenceImpl.name(ThreadReferenceImpl.java:270)
at
org.eclipse.jdt.internal.debug.core.model.JDIThread.getName(JDIThread.java:942)
at
org.eclipse.jdt.internal.debug.core.model.JDIThread$AsyncThread.addRunnable(JDIThread.java:2455)
at
org.eclipse.jdt.internal.debug.core.model.JDIThread.queueRunnable(JDIThread.java:682)
at
org.eclipse.jdt.internal.debug.ui.JavaDetailFormattersManager$3.run(JavaDetailFormattersManager.java:124)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java)
at
org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java)
at org.eclipse.swt.widgets.Display.release(Display.java:1598)
at org.eclipse.swt.graphics.Device.dispose(Device.java:212)
at org.eclipse.ui.internal.Workbench.run(Workbench.java:1390)
at
org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.java:858)
at org.eclipse.core.boot.BootLoader.run(BootLoader.java:461)
at java.lang.reflect.AccessibleObject.invokeL(AccessibleObject.java:207)
at java.lang.reflect.Method.invoke(Method.java:271)
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)
=========================================
!SESSION Jul 30, 2004 12:09:19.656
---------------------------------------------
java.fullversion=J2RE 1.3.1 IBM J9 build 20030702 (JIT enabled)
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Command-line arguments: -os win32 -ws win32 -arch x86 -data
C:\WebSphere\workspace_libdev -install file:C:/WebSphere/Studio5/eclipse/
!ENTRY org.eclipse.debug.core 4 2 Jul 30, 2004 12:09:19.656
!MESSAGE Problems occurred when invoking code from plug-in:
"org.eclipse.debug.core".
!STACK 0
java.lang.UnsupportedOperationException
at java.lang.Throwable.(Throwable.java)
at java.util.AbstractList.add(AbstractList.java:163)
at java.util.AbstractList.add(AbstractList.java:101)
at
com.ibm.debug.sqlj.internal.core.SQLJThread.refreshStackFrames(SQLJThread.java)
at
com.ibm.debug.sqlj.internal.core.SQLJThread.computeStackFrames(SQLJThread.java)
at
com.ibm.debug.sqlj.internal.core.SQLJThread.getStackFrames(SQLJThread.java)
at
com.ibm.debug.wsa.internal.core.WSAJavaThread.refreshStackFrames(WSAJavaThread.java)
at
com.ibm.debug.wsa.internal.core.WSAJavaThread.computeStackFrames(WSAJavaThread.java)
at
com.ibm.debug.wsa.internal.core.WSAJavaThread.getWSAStackFrame(WSAJavaThread.java)
at
com.ibm.debug.wsa.internal.core.WSAJavaThread.getTopWSAStackFrame(WSAJavaThread.java)
at
com.ibm.debug.wsa.internal.core.WSAJavaThread.handleBreakpointHit(WSAJavaThread.java)
at
com.ibm.debug.wsa.internal.core.WSAJavaThread.handleDebugEvents(WSAJavaThread.java)
at
com.ibm.debug.wsa.internal.core.WSADebugTarget.filterDebugEvents(WSADebugTarget.java)
at org.eclipse.debug.core.DebugPlugin$EventNotifier.run(DebugPlugin.java)
at
org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.java)
at org.eclipse.core.runtime.Platform.run(Platform.java)
at
org.eclipse.debug.core.DebugPlugin$EventNotifier.dispatch(DebugPlugin.java)
at org.eclipse.debug.core.DebugPlugin.fireDebugEventSet(DebugPlugin.java)
at
com.ibm.debug.sqlj.internal.core.SQLJDebugElement.fireEventSet(SQLJDebugElement.java)
at
com.ibm.debug.sqlj.internal.core.SQLJDebugElement.fireEvent(SQLJDebugElement.java)
at
com.ibm.debug.sqlj.internal.core.SQLJDebugElement.fireSuspendEvent(SQLJDebugElement.java)
at
com.ibm.debug.sqlj.internal.core.SQLJThread.setSuspended(SQLJThread.java)
at
com.ibm.debug.sqlj.internal.core.SQLJThread.setSuspended(SQLJThread.java)
at
com.ibm.debug.sqlj.internal.core.SQLJThread.doActionRequest(SQLJThread.java)
at
com.ibm.debug.sqlj.internal.core.SQLJThread.handleDebugEvents(SQLJThread.java)
at
com.ibm.debug.sqlj.internal.core.SQLJDebugTarget.filterDebugEvents(SQLJDebugTarget.java)
at org.eclipse.debug.core.DebugPlugin$EventNotifier.run(DebugPlugin.java)
at
org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.java)
at org.eclipse.core.runtime.Platform.run(Platform.java)
at
org.eclipse.debug.core.DebugPlugin$EventNotifier.dispatch(DebugPlugin.java)
at org.eclipse.debug.core.DebugPlugin.fireDebugEventSet(DebugPlugin.java)
at
org.eclipse.jdt.internal.debug.core.EventDispatcher.fireEvents(EventDispatcher.java)
at
org.eclipse.jdt.internal.debug.core.EventDispatcher.dispatch(EventDispatcher.java)
at
org.eclipse.jdt.internal.debug.core.EventDispatcher.run(EventDispatcher.java:211)
at java.lang.Thread.run(Thread.java:801)
Do you Yahoo!?
Yahoo! Mail - Helps protect you from nasty viruses.
_______________________________________________
platform-debug-dev mailing list
platform-debug-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/platform-debug-dev
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
