Return-Path: Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org Received: (qmail 36942 invoked from network); 4 Jul 2006 08:54:18 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 4 Jul 2006 08:54:18 -0000 Received: (qmail 80106 invoked by uid 500); 4 Jul 2006 08:54:17 -0000 Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org Received: (qmail 80078 invoked by uid 500); 4 Jul 2006 08:54:16 -0000 Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@jackrabbit.apache.org Delivered-To: mailing list dev@jackrabbit.apache.org Received: (qmail 80069 invoked by uid 99); 4 Jul 2006 08:54:16 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Jul 2006 01:54:16 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [209.237.227.198] (HELO brutus.apache.org) (209.237.227.198) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Jul 2006 01:54:16 -0700 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 34929714219 for ; Tue, 4 Jul 2006 08:52:31 +0000 (GMT) Message-ID: <28636572.1152003151211.JavaMail.jira@brutus> Date: Tue, 4 Jul 2006 08:52:31 +0000 (GMT+00:00) From: "Jukka Zitting (JIRA)" To: dev@jackrabbit.apache.org Subject: [jira] Updated: (JCR-412) JCA Concurrent Modification Exception when JCAManagedConnection.cleanup() called In-Reply-To: <77036675.1146019263005.JavaMail.root@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N [ http://issues.apache.org/jira/browse/JCR-412?page=all ] Jukka Zitting updated JCR-412: ------------------------------ Fix Version: 1.1 Version: 1.0.1 > JCA Concurrent Modification Exception when JCAManagedConnection.cleanup() called > -------------------------------------------------------------------------------- > > Key: JCR-412 > URL: http://issues.apache.org/jira/browse/JCR-412 > Project: Jackrabbit > Type: Bug > Components: jca > Versions: 1.0, 1.0.1 > Environment: JDK1.4.2 > SunOne AppServer 7 > Reporter: Ross Black > Assignee: Edgar Poce > Priority: Minor > Fix For: 1.1 > > The JCAManagedConnection.closeHandles() method causes a ConcurrentModificationException if the handles list is not empty. > This is caused by modification of the handles list by removeHandle(), while closeHandles() is iterating over the list. > Under SunOne AppServer 7 this can be caused simply by not closing the Session handle before the transaction commits. > It is probably not even necessary to send connectionClosed events during cleanup(). According to the API for connectionClosed, the event indicates that an application component has closed the connection handle. cleanup() is a container initiated action, and so the connectionClosed event is not applicable. > java.util.ConcurrentModificationException > at java.util.LinkedList$ListItr.checkForComodification(LinkedList.java:552) > at java.util.LinkedList$ListItr.next(LinkedList.java:488) > at org.apache.jackrabbit.jca.JCAManagedConnection.closeHandles(JCAManagedConnection.java:382) > at org.apache.jackrabbit.jca.JCAManagedConnection.cleanup(JCAManagedConnection.java:145) > at com.sun.enterprise.resource.IASPoolObjectImp.cleanup(IASPoolObjectImp.java:243) > at com.sun.enterprise.resource.IASGenericPoolObjects.transactionCompleted(IASGenericPoolObjects.java:794) > at com.sun.enterprise.resource.ResourcePoolManagerImpl.transactionCompleted(ResourcePoolManagerImpl.java:347) > at com.sun.enterprise.resource.ResourcePoolManagerImpl$SynchronizationListener.afterCompletion(ResourcePoolManagerImpl.java:644) > at com.sun.jts.jta.SynchronizationImpl.after_completion(SynchronizationImpl.java:70) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira