[
https://issues.apache.org/jira/browse/STANBOL-669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rupert Westenthaler updated STANBOL-669:
----------------------------------------
Component/s: (was: Enhancer)
Entity Hub
Description:
UPDATE: Further analyses have shown that the EventJobManager was not the cause
of this. See the 2nd comment for a proper description of this problem.
- - -
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.
was:
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.
Affects Version/s: entityhub-0.10.0-incubating
Summary: Proeprty <-> Field cache of the SolrYard is not
syncronized (was: EventJobManager does not corretly use Read/Write Locks on
EnhancementJobs)
> Proeprty <-> Field cache of the SolrYard is not syncronized
> -----------------------------------------------------------
>
> Key: STANBOL-669
> URL: https://issues.apache.org/jira/browse/STANBOL-669
> Project: Stanbol
> Issue Type: Bug
> Components: Entity Hub
> Affects Versions: entityhub-0.10.0-incubating
> Reporter: Rupert Westenthaler
> Assignee: Rupert Westenthaler
>
> UPDATE: Further analyses have shown that the EventJobManager was not the
> cause of this. See the 2nd comment for a proper description of this problem.
> - - -
> 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
