On Thu, Aug 14, 2003 at 11:39:12AM -0700, David Wheeler wrote:
On Thursday, August 14, 2003, at 07:58 AM, Perrin Harkins wrote:
You guys should just be using DBI-connect_cached then. It does
everything except the mod_perl cleanup handler.
Note that I still write a utility class that
On Thursday, August 14, 2003, at 12:53 PM, David Wheeler wrote:
Switching to connect_cached() seems to have made my problem with
Apache 1.3.28 go away Yay!
Did I say this? It's back today! :-(
Issuing rollback() for database handle being DESTROY'd without explicit
disconnect() at
On Thu, 14 Aug 2003, David Wheeler wrote:
On Thursday, August 14, 2003, at 01:15 PM, Rudy Lippan wrote:
Switching to connect_cached() seems to have made my problem with
Apache
1.3.28 go away Yay! Oh, and BTW, I am doing cleanup by running my
entire request in an eval:
Yes, but
On Friday, August 15, 2003, at 07:02 PM, Rudy Lippan wrote:
Inside the eval? What difference does it make? There are only a couple
of (controlled) commits and begins inside that eval, and any
exceptions
cause the whole thing to be rolled back.
No. The question is, 'What was happening inside of
On Thursday, August 14, 2003, at 11:39 AM, David Wheeler wrote:
Caching can be useful in some applications, but it can also cause
problems and should be used with care. The exact behaviour of this
method is liable to change, so if you intend to use it in any
production applications you should
On Thursday, August 14, 2003, at 01:15 PM, Rudy Lippan wrote:
Switching to connect_cached() seems to have made my problem with
Apache
1.3.28 go away Yay! Oh, and BTW, I am doing cleanup by running my
entire request in an eval:
Yes, but there still is the open question of what is happening in
On Thursday, August 14, 2003, at 07:58 AM, Perrin Harkins wrote:
You guys should just be using DBI-connect_cached then. It does
everything except the mod_perl cleanup handler.
Note that I still write a utility class that knows where to get the
database config and returns a connection, but I
On Wed, 2003-08-13 at 17:30, Matt Sergeant wrote:
Unfortunately Apache::DBI is an ugly action at a distance hack :-)
I agree, but having everyone implement their own is worse. It leads to
lots of repeated work on solved problems. What would you suggest to fix
it?
My idea would be to leave
On Wed, 13 Aug 2003, David Wheeler wrote:
On Wednesday, August 13, 2003, at 12:32 PM, David Wheeler wrote:
I'm attempting to isolate the problem now.
What version of DBD::Pg are you using for this test? Version of mod_perl?
The code that's causing the hangup looks like this:
our
On Wednesday, Aug 13, 2003, at 21:24 Europe/London, Perrin Harkins
wrote:
On Wed, 2003-08-13 at 16:07, David Wheeler wrote:
On Wednesday, August 13, 2003, at 12:32 PM, David Wheeler wrote:
The code that's causing the hangup looks like this:
First, we all need to yell at you for not using
On Thu, 14 Aug 2003, David Wheeler wrote:
On Thursday, August 14, 2003, at 11:39 AM, David Wheeler wrote:
Caching can be useful in some applications, but it can also cause
problems and should be used with care. The exact behaviour of this
method is liable to change, so if you intend
On Wednesday, Aug 13, 2003, at 22:46 Europe/London, Perrin Harkins
wrote:
My idea would be to leave Apache::DBI as it is for use with legacy CGI
code and then add a new module to the distribution that is called
explicitly so it has no distance issues. Maybe call it
Apache::DBI::Factory?
There
On Wednesday, August 13, 2003, at 01:24 PM, Perrin Harkins wrote:
On Wednesday, August 13, 2003, at 12:32 PM, David Wheeler wrote:
The code that's causing the hangup looks like this:
First, we all need to yell at you for not using Apache::DBI. Your code
is not doing anything that it doesn't
On Wed, 13 Aug 2003, David Wheeler wrote:
You can see that this gets really ugly. Anyone seen anything like
this,
or have any idea what could be causing these problems?
Try changing your ping method or removing the ping and see if the
problem persists.
Not sure I want to go into
Perrin Harkins wrote:
On Wed, 2003-08-13 at 17:30, Matt Sergeant wrote:
Unfortunately Apache::DBI is an ugly action at a distance hack :-)
I agree, but having everyone implement their own is worse. It leads to
lots of repeated work on solved problems. What would you suggest to fix
it?
My idea
On Wednesday, August 13, 2003, at 02:03 PM, Rudy Lippan wrote:
What version of DBD::Pg are you using for this test? Version of
mod_perl?
1.30 from CVS a couple of weeks ago, but I've seen it with 1.22, too.
Does this happen on every second request to httpd, or is it more
intermittent?
On Wed, 2003-08-13 at 16:31, David Wheeler wrote:
Try changing your ping method or removing the ping and see if the
problem persists.
Not sure I want to go into hacking DBD::Pg's internals at this point...
Just remove the ping check from your _connect code and see what happens.
- Perrin
On Wednesday, August 13, 2003, at 08:27 PM, Rudy Lippan wrote:
So then it is nothing that I did ;)
No, probably something I did. :-)
Intermittent.
But always on the second requst to the first process?
Nope.
It looks like something is happening to the Postgresql connection,
which
is throwing
On Wed, 13 Aug 2003, David Wheeler wrote:
On Wednesday, August 13, 2003, at 02:03 PM, Rudy Lippan wrote:
What version of DBD::Pg are you using for this test? Version of
mod_perl?
1.30 from CVS a couple of weeks ago, but I've seen it with 1.22, too.
So then it is nothing that I did
19 matches
Mail list logo
