ibatis-user-java mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adam Gugliciello" <Ad...@emeta.com>
Subject RE: ThrottledPool handing
Date Mon, 15 Aug 2005 18:33:24 GMT
good point, it may be excepting and losing sessions, I'll close the sessions in a finally block.


From: Niels Beekman [mailto:n.beekman@wis.nl]
Sent: Mon 8/15/05 2:29 PM
To: user-java@ibatis.apache.org
Subject: RE: ThrottledPool handing



Can you simulate what happens when


> t.execute(this.sqlMapClient)


throws an exception, so before you explicitly close the session?





From: Clinton Begin [mailto:clinton.begin@gmail.com] 
Sent: maandag 15 augustus 2005 19:19
To: user-java@ibatis.apache.org
Subject: Re: FW:


Why does it take a minute to get a connection?  With a connection pool, it should literally
be milliseconds....


On 8/15/05, Adam Gugliciello <AdamG@emeta.com> wrote:

Under a heavy sustained load, the sqlmaps ThrottledPool seems to start to bind, the the vast
majority of them binding up and blocking waiting to build a new session, and stay blocked
long after the fact, even days after the request has been abandoned. Any help would be appreciated,
and I am attaching a thread dump.


My code looks like:


 private void executeSqlMapTemplate(SqlMapTemplate t) throws SQLException
        final Connection c =
                        1 * 60 * 1000l); // Waits a minute for a connection
        if (c == null)
            throw new IllegalStateException("Unable to retrieve JDBC Connection from db pool.");
            SqlMapSession sess=this.sqlMapClient.openSession(c);







View raw message