Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Message-ID: <339882512.432801269347367144.JavaMail.jira@brutus.apache.org>
Date: Tue, 23 Mar 2010 12:29:27 +0000 (UTC)
From: "Kevan Miller (JIRA)" <jira@apache.org>
To: dev@geronimo.apache.org
Subject: [jira] Resolved: (GERONIMO-5200) high cpu load, probably result of
 concurrent access of resourcesNotFound in MultiParentClassLoader
In-Reply-To: <1136105897.427621269327027129.JavaMail.jira@brutus.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/GERONIMO-5200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kevan Miller resolved GERONIMO-5200.
------------------------------------

    Resolution: Fixed

Should be fixed. Now using ConcurrentHashMap, instead of HashSet.

> high cpu load, probably result of concurrent access of resourcesNotFound in MultiParentClassLoader
> --------------------------------------------------------------------------------------------------
>
>                 Key: GERONIMO-5200
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-5200
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: core
>    Affects Versions: 2.1.4, 2.2
>         Environment: Linux 64 bits, geronimo 2.2 build 2009.12.07-18:20:06.045-0800
>            Reporter: Marco Laponder
>            Assignee: Kevan Miller
>             Fix For: 2.1.5, 2.2.1
>
>         Attachments: thread.dump
>
>
> Sometimes during the use of our webapplication the cpu of our server has extereme high load caused by geronimo which stays high forever untillI stop geronimo. I have created a thread dump when the cpu load is high (attached to this jira).  Suspicious in this thread dump are multiple thread in the containsKey. 
> As not all the access of the resourcesNotFOund map is not synchronized this could be the cause of the problem as this might result in a infinite loop when the contains method is called during a map resize. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.