Thanks much Thomas.
So far, the reporter has been great about responding to requests,
so my guess is he'll come up with the desired info.
BTW...others might be interested in this...the bug reporter has
been using Equinox + ECF Remote Services to do some interesting
work on 'Service Oriented Evolutionary Algorithms'. See [1] for
his description.
Scott
[1]
http://osgiliath.org/2013/01/16/service-oriented-evolutionary-algorithms-paper-has-been-accepted/
On 1/17/2013 11:42 AM, Thomas Watson wrote:
Hi Scott,
I added comments to the bug. I
suspect it is a deadlock caused by locks in the DS and/or
framework implementations. But at this point it is just a
guess. Hopefully the bug reporter can help out by generating
a thread dump for us to look at.
Tom
 Scott Lewis
---01/17/2013 11:51:11 AM---Greetings, We/ECF uses Equinox
event for our implementation of the Remote Service
From: Scott Lewis
<slewis@xxxxxxxxxxxxx>
To: Equinox development mailing list
<equinox-dev@xxxxxxxxxxx>,
Date: 01/17/2013 11:51 AM
Subject: [equinox-dev] equinox event
question
Sent by: equinox-dev-bounces@xxxxxxxxxxx
Greetings,
We/ECF uses Equinox event for our implementation of the Remote
Service
Admin specification. One of our consumers has been using ECF
remote
services/RSA, Equinox, DS and their own code, and has
experienced a
problem that we are attempting to diagnose.
See the full description on this bug [1]. As you can see on
the bug,
the error message that they are apparently getting when the
remote
service export fails is:
!ENTRY org.eclipse.equinox.ds 2 0 2013-01-14 20:46:42.134
!MESSAGE [SCR] Enabling components of bundle
org.eclipse.equinox.event
did not complete in 30000 msÂ
!ENTRY org.eclipse.equinox.ds 2 0 2013-01-14 20:46:42.135
!MESSAGE [SCR - WorkThread] Timeout occurred! Thread was
blocked on
processing [QueuedJob] WorkPerformer:
org.eclipse.equinox.internal.ds.SCRManager@19336006;
actionType 1
This apparently happens intermittently at startup.
Couple of questions for Equinox folks: Does anything about
this error
message (for org.eclipse.equinox.event) look
familiar/understandable?
Is it possible that a race on startup is causing this?
Also...for the DS folks...is there any option that will get DS
to report
the component where the thread was blocked? It would be very
helpful
for us to be able to understand where this is happening (i.e.
whether
it's consistently on a given component, etc).
Thanksinadvance,
Scott
[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=398321
_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev
_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev
|
