Joern Janoschek wrote:
>
> On Wed, 14 Mar 2001 18:46:31 +0000, Greg Cope wrote:
>
> >There's no reason why Apache::DBI should not work - by the sounds of it
> >the connections strings may have been different ?
> >
> >Apache::DBI works in an environment where on user ID is used to connect
> >to the DB mulitple time. If you use two different connection strings
> >Apache::DBI will try and make both persistent (IIRC).
> >
> >So check your DBI connection strings as they should be indentical.
>
> Here is the problem: The connection strings _are_ the same. No
> change at all between two connects... same host, same user, same
> DB, even the same table (not that it bothers)... nothing
> changes. That's the strange thing and that's what we didn't
> understand at all and what pushed us to the point where we
> disabled Apache::DBI.
> Could it be that there is a connection between the socket
> problem and the ever rising persistent connections? Maybe the
> Apache::DBI cannot share an already connected handle because the
> system says the socket is still in use and not free at all. That
> would explain the unusual behaviour of Apache::DBI...
> Maybe someone who hasn't an explaination could tell me at least
> where to look at? Linux system? Apache? mod_perl? Mysql?
> DBI/DBD?
>
This would appear to be a DBI problem - but I'm no expert. Have you
tried the DBI list ?
I am afraid I can shed no further light on this.
Greg
> Thanks anyway,
>
> Jörn Janoschek.
> KLAHOLD - We make IT work! - http://www.klahold.de
> - WebDevelopment - http://www.klahold.de
> - Content-Management-System - http://www.interred.de
