Did I find a bug or is this expected behavior?
Don't know. Generally DBCP pool is very stable. So it is hard to say
without actually getting to the cause of the problem.
Andrus
On Feb 15, 2007, at 1:57 PM, Øyvind Harboe wrote:
On 2/14/07, Andrus Adamchik <[EMAIL PROTECTED]> wrote:
Just
On 2/14/07, Andrus Adamchik <[EMAIL PROTECTED]> wrote:
Just a guess without digging through the code details - a different
DataSource implementation in Tomcat (DBCP) does something
differently. Try using the same DataSource you used in Jetty.
Did I find a bug or is this expected behavior?
Bein
On 2/14/07, Andrus Adamchik <[EMAIL PROTECTED]> wrote:
Just a guess without digging through the code details - a different
DataSource implementation in Tomcat (DBCP) does something
differently. Try using the same DataSource you used in Jetty.
I changed my connection config in Tomcat as below an
Just a guess without digging through the code details - a different
DataSource implementation in Tomcat (DBCP) does something
differently. Try using the same DataSource you used in Jetty.
Andrus
On Feb 14, 2007, at 9:05 AM, Øyvind Harboe wrote:
We've been using a modified DataPort w/Jetty
We've been using a modified DataPort w/Jetty for a while and never had
any problems.
However, today we tried running it under Tomcat and it failed.
Paraphrased from my source, I do the following:
SelectQuery select = new SelectQuery(entity);
select.setFetchingDataRows(true);
IteratedSelectObs
