[naacba]

Hi
I am working in a multithreading application, which I need to debug remotelly.
The app is running in a Websphere 6.0 application server.
Given the complexity of the threading and types hierarchied implemented in the app, I need to use a set of conditions before I add a breakpoint in the main classes, but when I add a conditional breakpoint I am getting this exception:
Title: Conditional Breakpoint Error
Description: Conditional breakpoint encountered runtime exception.
Reason:
com.sun.jdi.ObjectCollectedException occurred invoking method

The line that I am adding the breakpoint in says this
eventManager.processEvent(request);

The breapoint condition asks for this
request.getEventType().equals(“TYPE_ID_1”)

I found a bunch of bugs in eclipse that seem to be related to this, that leaded me to this
https://bugs.eclipse.org/bugs/show_bug.cgi?id=269231
It should have been fixed in milestone 3.5 M7 and I am using myecplipse 9.0M1 that seems to use Eclipse 3.6.0 so I assume this fix was included

this is what I have in the log in .metadata folder
!ENTRY org.eclipse.jdt.debug 4 125 2010-12-27 17:13:25.785
!MESSAGE Internal error logged from JDI Debug:
!STACK 0
com.sun.jdi.ObjectCollectedException
at org.eclipse.jdi.internal.MirrorImpl.defaultReplyErrorHandler(MirrorImpl.java:241)
at org.eclipse.jdi.internal.ObjectReferenceImpl.disableCollection(ObjectReferenceImpl.java:99)
at org.eclipse.jdt.internal.debug.core.model.JDIObjectValue.disableCollection(JDIObjectValue.java:418)
at org.eclipse.jdt.internal.debug.eval.ast.engine.Interpreter.disableCollection(Interpreter.java:114)
at org.eclipse.jdt.internal.debug.eval.ast.engine.Interpreter.push(Interpreter.java:100)
at org.eclipse.jdt.internal.debug.eval.ast.instructions.Instruction.pushNewValue(Instruction.java:182)
at org.eclipse.jdt.internal.debug.eval.ast.instructions.PushString.execute(PushString.java:26)
at org.eclipse.jdt.internal.debug.eval.ast.engine.Interpreter.execute(Interpreter.java:66)
at org.eclipse.jdt.internal.debug.eval.ast.engine.ASTEvaluationEngine$1$EvaluationRunnable.run(ASTEvaluationEngine.java:483)
at org.eclipse.jdt.internal.debug.core.model.JDIThread.runEvaluation(JDIThread.java:681)
at org.eclipse.jdt.internal.debug.eval.ast.engine.ASTEvaluationEngine$EvalRunnable.run(ASTEvaluationEngine.java:520)
at org.eclipse.jdt.internal.debug.core.model.JDIThread$ThreadJob.run(JDIThread.java:2756)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)

Any hint on this will be very appreciated.

[Brian Fernandes]

naacba,

Can you tell me how you established the remote debugging connection? And are you using MyEclipse or MyEclipse Blue?

Regardless, as you pointed out I’m afraid this will be an issue with the JDT, something which we have no control over. Either the issue is different from the Eclipse bug you have identified or the bug is still not correctly fixed. The bug mentions an issue in cases where conditional breakpoints call a method which itself has a breakpoint in it. If this is your case, does removing the breakpoint from the method fix the problem?

[Author]

Posts