I'm sorry to bother with the developers, but I'm not getting anywhere with
this problem.
---------- Forwarded message ----------
From: Glenn Barnard <barnardgl...@gmail.com>
Date: Thu, May 28, 2009 at 11:44 AM
Subject: DB Error
To: user-j...@ibatis.apache.org
Hi, all…I’ve been using Ibatis for several months now to build an internal
web application. We’re using connection pooling and so far so good. So now
I’m trying to use the same connection pools for batch applications that are
scheduled to run via a chron type function from the same webserver. Those
jobs run fine on our development boxes without connection pooling (i.e., as
Junit processes). But when I try to run them from the webserver, I get a few
of these errors and then all the connections become useless quickly and I
have to restart the webserver. The errors start with the message:
Unable to set AutoCommit property.SET CHAINED command not allowed within
multi-statement transaction.
Then as the connections become useless, the following messages start coming
out. This message I would expect after the pool is exhausted.
Error in allocating a connection. Cause: In-use connections equal
max-pool-size and expired max-wait-time. Cannot allocate more connections
What’s really perplexing me is that this happens on SELECT statements, and
not just INSERT or UPDATE statements.
I’ve Googled this error and am not getting anywhere. I’ve also reviewed the
connection pool settings and no amount of tweaking improves the situation.
Any help would be most appreciated.
Our environment consists of:
Java 1.6
Spring 2.5
Ibatis
Glassfish/* Sun Java System Application Server 9.1 (build
b58g-fcs) *(webserver)**
Sybase 12.5
