This content has been marked as final.
Show 4 replies
-
1. Re: ThreadPoolDispatcher shutdown issue
kapitanpetko Dec 11, 2009 2:33 AM (in response to armsargis)Override the default dispatcher with your own component and see how it work out.
-
2. Re: ThreadPoolDispatcher shutdown issue
armsargis Dec 11, 2009 11:14 AM (in response to armsargis)What you mean by 'Override the default dispatcher' it means I need to copy all code from 'default dispatcher' in my component and try it? also there is some package level access code in. 'default dispatcher'.
And in general:
executor.shutdown(); try { boolean isDone = executor.awaitTermination(5, TimeUnit.SECONDS); if(!isDone) { executor.shutdownNow(); } } catch (InterruptedException ie) { // ignore }
I tested it in many situation it was ok.
-
3. Re: ThreadPoolDispatcher shutdown issue
kapitanpetko Dec 11, 2009 1:12 PM (in response to armsargis)
Sargis Harutyunyan wrote on Dec 11, 2009 11:14:
What you mean by 'Override the default dispatcher' it means I need to copy all code from 'default dispatcher' in my component and try it? also there is some package level access code in. 'default dispatcher'.I mean define a component with the same name and higher precedence, so that it gets installed instead of the default one. Package level is unfortunate, if that is the case you might have to copy the code. In any case, file a JIRA.
-
4. Re: ThreadPoolDispatcher shutdown issue
armsargis Dec 12, 2009 7:59 AM (in response to armsargis)I have sources of Seam from repo so I will modify directly seam code and build it and deploy in my application to see and test how it works.
Thanks.