Return-Path: Delivered-To: apmail-jackrabbit-users-archive@minotaur.apache.org Received: (qmail 34406 invoked from network); 4 Oct 2010 09:08:29 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 4 Oct 2010 09:08:29 -0000 Received: (qmail 7817 invoked by uid 500); 4 Oct 2010 09:08:29 -0000 Delivered-To: apmail-jackrabbit-users-archive@jackrabbit.apache.org Received: (qmail 7598 invoked by uid 500); 4 Oct 2010 09:08:26 -0000 Mailing-List: contact users-help@jackrabbit.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@jackrabbit.apache.org Delivered-To: mailing list users@jackrabbit.apache.org Received: (qmail 7588 invoked by uid 99); 4 Oct 2010 09:08:25 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Oct 2010 09:08:25 +0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of jukka.zitting@gmail.com designates 209.85.214.170 as permitted sender) Received: from [209.85.214.170] (HELO mail-iw0-f170.google.com) (209.85.214.170) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Oct 2010 09:08:17 +0000 Received: by iwn37 with SMTP id 37so14143363iwn.1 for ; Mon, 04 Oct 2010 02:07:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:received:in-reply-to :references:from:date:message-id:subject:to:content-type; bh=R3hUvTgQKyOb2KuYPeDyKIn06452JRalU3Cys7zYX3M=; b=n+FzuSiqqO2ZdfpRKxXvNWEP/F1oXqFigcycbShqSYCHcqQjq2cDpgfmYMz2/yFKcr CaGc84y5B6EdnBeGx1HEJhMODdUbVnImQBx7gMWv1H90krinywbzXNNU91WRdc4HM7rt UmmFs6M5BsCwNMQ+i6V1nTa/KfmbaqajsfZWc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; b=BTwiHK2eR3zNFL06mK2l55cmvkI5KAqPPuLeNiTXbIDkMibbikT57pSp9bM5ULOuBS Pi2BIwarLfNk5bgsp8E2JjxIpLZT55urcaXK3mZ5hkQejfSbj4D0s/42flT1CJJJWgam scvz+vzLJOFSOgi89ronhBteSz7CdL+Xpy8CE= Received: by 10.231.85.206 with SMTP id p14mr9887028ibl.89.1286183276253; Mon, 04 Oct 2010 02:07:56 -0700 (PDT) MIME-Version: 1.0 Received: by 10.231.207.74 with HTTP; Mon, 4 Oct 2010 02:07:35 -0700 (PDT) In-Reply-To: References: From: Jukka Zitting Date: Mon, 4 Oct 2010 11:07:35 +0200 Message-ID: Subject: Re: Unclosed session detected. The session was opened here To: users@jackrabbit.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org Hi, On Mon, Oct 4, 2010 at 10:59 AM, Narendra Sharma wrote: > 1. What does this exception mean? This warnings is logged when the JVM reclaims an unreferenced Session as garbage. It signals a code path that opens a new session but then forgets to properly close once the session is no longer used. The included stack trace is meant to help locate the troublesome code path. > 2. Is it harmful? Jackrabbit will automatically close the stray session in such cases, so the only real harm done is that the unclosed session has unnecessarily tied up system resources that could have been released already before. > 3. Can this result in abrupt session close and operation failure? No. The session is only automatically closed once the JVM reclaims it as garbage, i.e. once there are no other references to the session. > 4. What triggers this exception? Garbage collection. > 5. I use a Session cache which holds and reuses session for same user > operations. Two different users don't share the same session. The session > may be live for long duration (few minutes) if user keep performing > operations. Could this use case result into this exception? Only if your Session cache leaks. BR, Jukka Zitting