Mailing-List: contact dev-help@ibatis.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ibatis.apache.org
Message-ID: <731120842.1250342354914.JavaMail.jira@brutus>
Date: Sat, 15 Aug 2009 06:19:14 -0700 (PDT)
From: "Clinton Begin (JIRA)" <ibatis-dev@incubator.apache.org>
To: dev@ibatis.apache.org
Subject: [jira] Closed: (IBATIS-533) Thread blocking on AutoResultMap
In-Reply-To: <2021076967.1219939004247.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Clinton Begin closed IBATIS-533.
--------------------------------

    Resolution: Fixed

> Thread blocking on AutoResultMap
> --------------------------------
>
>                 Key: IBATIS-533
>                 URL: https://issues.apache.org/jira/browse/IBATIS-533
>             Project: iBatis for Java
>          Issue Type: Bug
>    Affects Versions: 2.3.2
>            Reporter: Robert McIntosh
>            Priority: Critical
>
> The AutoResultMap class' getResults method is synchronized. This causes threads to get backed up when a moderate load is on the system. The end result is that our heap gets overloaded and eventually the app stops.
> it appears from looking at the code that the synchronize only needs to be on the remapping and/or initial construction of the result mappings. Would suggest making the the initialize method synchronized at the very least, so that once the mapping is created no blocking of threads is necessary.
> May be related to issue 519 as well.

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


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ibatis.apache.org
For additional commands, e-mail: dev-help@ibatis.apache.org