[jira] [Commented] (STANBOL-669) EventJobManager does not corretly use Read/Write Locks on EnhancementJobs

["Rupert Westenthaler (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/STANBOL-669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13403902#comment-13403902 ] 

Rupert Westenthaler commented on STANBOL-669:
---------------------------------------------

the reproduce able issue was related to logging only (used the live list instead of the copy created within a read-lock). Further investigating to confirm or to rule this out.
                
> EventJobManager does not corretly use Read/Write Locks on EnhancementJobs
> -------------------------------------------------------------------------
>
>                 Key: STANBOL-669
>                 URL: https://issues.apache.org/jira/browse/STANBOL-669
>             Project: Stanbol
>          Issue Type: Bug
>          Components: Enhancer
>            Reporter: Rupert Westenthaler
>            Assignee: Rupert Westenthaler
>
> When bombarding the enhancer with multiple concurrent EnhancementJobs the EvenJobManager might not correctly process all requests due to changes that do not correctly apply a writeLock on the EnhancementJob.
> As fixing those things is not an easy thing I implemented already an new Integration-Test that allows to send long abstracts from dbpedia as content to the enhancer. The integration-test includes enough data for 10.000 requests. It uses "java.util.concurrent.ExecutorService" for async Requests and the "PoolingClientConnectionManager" of apache http commons for sending multiple parallel requests.
> Setting this to 1000 requests with 10 threads lets easily to reproduce the problem.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira