You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nutch.apache.org by "Enis Soztutar (JIRA)" <ji...@apache.org> on 2007/04/24 10:21:15 UTC
[jira] Updated: (NUTCH-471) Fix synchronization in NutchBean
creation
[ https://issues.apache.org/jira/browse/NUTCH-471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Enis Soztutar updated NUTCH-471:
--------------------------------
Attachment: NutchBeanCreationSync_v1.patch
this patch synchronizes NutchBean.get((ServletContext app, Configuration conf) using servlet context as mutex. (NutchBean)app.getAttribute("nutchBean") is checked twice, the first one is not synchronized for performance reasons.
> Fix synchronization in NutchBean creation
> -----------------------------------------
>
> Key: NUTCH-471
> URL: https://issues.apache.org/jira/browse/NUTCH-471
> Project: Nutch
> Issue Type: Bug
> Components: searcher
> Affects Versions: 1.0.0
> Reporter: Enis Soztutar
> Fix For: 1.0.0
>
> Attachments: NutchBeanCreationSync_v1.patch
>
>
> NutchBean is created and then cached in servlet context. But NutchBean.get(ServletContext app, Configuration conf) is not syncronized, which causes more than one instance of the bean (and DistributedSearch$Client) if servlet container is accessed rapidly during startup.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.