Mailing-List: contact user-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@geronimo.apache.org
Received-SPF: pass (nike.apache.org: domain of lists@nabble.com designates
 216.139.236.158 as permitted sender)
Message-ID: <25772925.post@talk.nabble.com>
Date: Tue, 6 Oct 2009 10:13:09 -0700 (PDT)
From: ericp56 <eric.phetteplace@twcable.com>
To: user@geronimo.apache.org
Subject: Re: A lock could not be obtained within the time requested
In-Reply-To: <6BFCD729-0597-44CC-AC84-DBDEDDD992EC@yahoo.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <25771661.post@talk.nabble.com>
 <6BFCD729-0597-44CC-AC84-DBDEDDD992EC@yahoo.com>


I'm using 2.1.3.  There is no stack trace that's useful.  It's just that
there are lock on the table, even there is nothing being monitored, or
listed as being monitored under monitoring:

Running this command in ActiveMRCDB:
select * from SYSCS_DIAG.STATEMENT_CACHE

I see lots of entries like this:
 	SELECT S.statsValueList AS statsValueList, M.statsNameList AS
statsNameList, S.snapshot_time AS snapshot_time, M.mbeanName AS mbeanName
FROM Statistics S, MBeans M WHERE S.snapshot_time=1242698019775 AND
S.mbeanId=M.id

In ArchiveMRCDB, I see lots of these:

INSERT INTO Statistics (snapshot_time, statsValueList, mbeanId) VALUES
(1242875019775,'0,0,0,-1,0,0,0,0,0,0,1',68)

Apparently there's still a flurry of monitoring activity going on.

Eric
-- 
View this message in context: http://www.nabble.com/A-lock-could-not-be-obtained-within-the-time-requested-tp25771661s134p25772925.html
Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.