Re^2: DBI seems to randomly die

I've tested this in an environment where I am the only user and I am still seeing this. If it fails, it dies at the point I issue a drop table on the merge tables (where I commented it in my code snippet). No errors, hanging, or anything. I just get a blank screen. very frustrating. My gut feeling is also possibility of open tables on windows. But I can't seem to identify it consistantly. Even monitoring "show open tables"

I appreciate your feedback

/- M a r c -/

Comment on Re^2: DBI seems to randomly die

Replies are listed 'Best First'.
Re^3: DBI seems to randomly die by dsheroh (Monsignor) on Jun 06, 2006 at 20:10 UTC
You're not seeing anything at all in your browser, not even the output of the `print qq {<hr>\n} if ($mysqlDebug); print qq {$DatabaseName, $dbS, $dbU, $dbP, $mergeCount, $RemoteAdd +r, $routers<br>\n} if ($mysqlDebug);` [download] lines at the top of the sub? If you're not even seeing that (and you have $mysqlDebug set, of course), then have you tried using telnet to port 80 and/or a packet sniffer to see the complete document returned by apache (including headers and anything else that your browser may eat without displaying it)?	[reply] [d/l]
Re^4: DBI seems to randomly die by FitTrend (Pilgrim) on Jun 06, 2006 at 20:21 UTC
Yes. If I enable that variable then I see everything until the drop statement. I print the drop statement debug prior to the execusion to make sure they are being issued and it consistently stops on the first. Even if I re-arrange the order :( /- M a r c -/	[reply]


P is for Practical
	PerlMonks