Hi Tim,
*** Thank you very much for your reply!
> There may be relevant lines above or below the ones you've quoted.
> Please post them as well.
>
> Enabling tracing (see DBI docs) would help identify what's happening
> when this message (from sv_dump) is produced.
*** The error lines I posted are all there is. There is nothing before
them or after them.
I have tried to bracket the problem in time by producing my own error
that I use as a "mark" in the apache error log. No matter where I put
my "mark" error, it occurs BEFORE the problem. So the problem is
occurring after my application finishes ALL its DBI work, and all that
remains is to spit out the HTML.
So I suspected some kind of "shutdown" problem. I added code to call
disconnect() for every single dbh in the system. No difference :(.
Didn't really expect one: the documentation is clear that disconnect()
is not really needed. But I was not sorry to add it: I tend to be
suspicious of magic initializations and shutdowns - a sad effect of 20
years of embedded C programming. :)
I will enable tracing later today and report the results.
- Jerry Kaidor
