sorry for additional post (and rich text format), but upon further investigation, this is probably not DBI, having removed all my DBI calls, I find now that I get the following in Perl debugger (line 964 is the last line of the child)
964: print STDOUT "$spoolfile\n"; DB<2> s POE::Wheel::Run::new(/sbcimp/run/pkgs/CORE/11.2.0/links/cpan/lib/POE/Wheel/Run.pm:378): 378: close STDOUT if defined fileno(STDOUT); DB<2> POE::Wheel::Run::new(/sbcimp/run/pkgs/CORE/11.2.0/links/cpan/lib/POE/Wheel/Run.pm:379): 379: close STDERR if defined fileno(STDERR); DB<2> POE::Wheel::Run::new(/sbcimp/run/pkgs/CORE/11.2.0/links/cpan/lib/POE/Wheel/Run.pm:381): 381: eval { POSIX::_exit(0); }; DB<2> POE::Wheel::Run::new(/sbcimp/run/pkgs/CORE/11.2.0/links/cpan/lib/POE/Wheel/Run.pm:381): 381: eval { POSIX::_exit(0); }; DB<2> and the parent has gone into a sleep from which it never wakes This doesn't happen when testing with the childtest3 example, which produces the same kind of output from the child, but the parent continues as you would expect Any ideas please - I've spent a day trying to figure this out already. -- David -----Original Message----- From: Ferrington, David Sent: 07 January 2004 00:47 To: '[EMAIL PROTECTED]' Subject: DBI in a Wheel::RUN Hello again, seams I'm having problems... I'm trying to use DBI, but can't use the DBI components, becuase getting them into this place will take longer than my deadline, so trying to impliment my own DBI code used from POE... I have a POE session that makes a connection via DBI to Sybase and performs a query. Based on query results, the session may then run a Wheel to fork a child to perform another longer query. Ideally, the first query connection will be left open, the firsts query is an alarmed event that runs again in 60 sec - however, closing the connection does not help prevent my problem. Even if the forked process does nothing but exit, the Perl debugger shows me it going through the DBI disconnect_all routine, that appears to exit the DBI module, but the child just terminates at that point. The parent appears to be sleeping (based on truss output), but NEVER comes back to the POE kernel, unless I interrupt it, in which case, all my queued events run at that point and then it exits in error. So my forked process appears to be blocking my main code and causing it to crash - suggestions? -- David Visit our website at http://www.ubs.com This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. If verification is required please request a hard-copy version. This message is provided for informational purposes and should not be construed as a solicitation or offer to buy or sell any securities or related financial instruments.