Hi,
From a colleague I heard that proxool is a very good pooling mechanism
for JDBC connections. The beautiful thing is, he is right! :-)
But, I have some problems implementing proxool in our current web
application. I get a lot of "[WARN] bog - -Unable to set status of
connection 1 from ACTIVEto AVAILABLE. It remains AVAILABLE" warnings en
it takes a lot of time before my data get's committed to the database.
Let me explain how it works on our side.
In a single transaction a couple of tables needs to be updated (about 5
of them) so what we do is setting autocommit off and add a number of
update / insert statements to a connections and commit them at the very
end. If anything goes wrong, we do a rollback and everything is fine
:-).
These connections are stored in a HashTable associated by the thread (we
only use 1 connection for each thread). But when I store a connection in
a thread an decide to add some statements later, I get the waning
mentioned in the subject. Why is this?
In all, I do not care about the warning. But it's makes the application
sluggish as a snail. (like it is waiting for timeouts).
Is there any way I can resolve this? By changing my code or even
Proxool? I have just multiple connections which all must be performed or
none at al I thought putting them in a HashTable by thread would be a
good idea, but is it?
With kind regards,
Leon
|
