Re: [Dltk-dev] DLTK thread dead lock

[Peter Klügl <pkluegl@xxxxxxxxxxxxxxxx>]

Thanks :-) I will try to modularize them again.

Best,

Peter

On 15.07.2013 13:28, Alexey Panchenko wrote:

Hi,

Right. If modularized correctly, then it's physically not possible :-)

What happens in this particular case: indexer is in the dltk.core (non-UI) and is started earlier. It tries to read some preferences, which are supposed to be in the core part of your IDE. Unfortunately, there is only one module, which includes UI, so deadlock happens.

There could be other similar cases.

Regards,

Alex

On Mon, Jul 15, 2013 at 1:18 PM, Peter Klügl <pkluegl@xxxxxxxxxxxxxxxx> wrote:

Hi,

the layout was originally the same as for the other IDEs, but the plugins have been merged for some reasons.

So, if the the different parts are modularized correctly, the indexer won't call the UI Preference initializer, right?

Thanks Alex, you helped me already a lot :-)

Best,

Peter

On 15.07.2013 13:06, Alexey Panchenko wrote:

Hi Peter,

It looks like all the code is contained in the single plugin project.

You'd better split the code into UI and non-UI projects, it's the most reliable way of solving this issue.

Regards,

Alex

On Mon, Jul 15, 2013 at 12:55 PM, Peter Klügl <pkluegl@xxxxxxxxxxxxxxxx> wrote:

Hi Alex,

thanks for the hint, I will investigate that.

The maven project for the IDE is here:
https://svn.apache.org/repos/asf/uima/sandbox/ruta/trunk/ruta-ep-ide

Best,

Peter

On 15.07.2013 11:19, Alexey Panchenko wrote:

Hi Peter,

DLTK indexing thread should not execute UI code at all, that's the problem.

Could you check that UI and non-UI code is properly separated?

I can give a look at the sources if you provide the link.

Regards,

Alex

On Mon, Jul 15, 2013 at 10:08 AM, Peter Klügl <pkluegl@xxxxxxxxxxxxxxxx> wrote:

Dear DLTK team,

I am developing an IDE based on DLTK for a rule-based information
extraction language at ASF. We have for some time problems with the
interaction of the DLTK threads and one of our components, an editor
implementation.

If the editor is open at eclispe start, then AFAIK two DLTK threads
(Indexing and UI) produce a deadlock, which can only resolved by
deactivating either my DLTK IDE or the editor.

Any idea what the problem might be or how to resolve it?

Our issue (with jstack output) is here:
https://issues.apache.org/jira/browse/UIMA-2528

Any pointers are greatly appreciated.

Best,

Peter
_______________________________________________
dltk-dev mailing list
dltk-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dltk-dev

_______________________________________________
dltk-dev mailing list
dltk-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dltk-dev

_______________________________________________
dltk-dev mailing list
dltk-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dltk-dev

_______________________________________________
dltk-dev mailing list
dltk-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dltk-dev

_______________________________________________
dltk-dev mailing list
dltk-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dltk-dev

_______________________________________________
dltk-dev mailing list
dltk-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dltk-dev