From: Eliot G. <eg...@br...> - 2010-07-01 14:49:55
|
I have done additional troubleshooting and I believe it may actually be an issue with pgpool-II abnormally exiting a child process and not releasing a connection properly or returning results, so iODBC just sits there waiting on pgpool-II. I don't have the time to troubleshoot further, however. Eliot Gable Senior Product Developer 1228 Euclid Ave, Suite 390 Cleveland, OH 44115 Direct: 216-373-4808 Fax: 216-373-4657 eg...@br... CONFIDENTIAL COMMUNICATION. This e-mail and any files transmitted with it are confidential and are intended solely for the use of the individual or entity to whom it is addressed. If you are not the intended recipient, please call me immediately. BROADVOX is a registered trademark of Broadvox, LLC. -----Original Message----- From: iODBC Maintainer [mailto:io...@op...] Sent: Thursday, July 01, 2010 10:45 AM To: iod...@li... Subject: Re: [Iodbc-bugs] Deadlock in Init_iODBC() at henv.c:281 Hi Eliot, > I am hitting a deadlock in iODBC-3.52.7: > > > > #0 0x000000332e60d4c4 in __lll_lock_wait () from /lib64/libpthread.so.0 > > No symbol table info available. > > #1 0x000000332e608e1a in _L_lock_1034 () from /lib64/libpthread.so.0 > > No symbol table info available. > > #2 0x000000332e608cdc in pthread_mutex_lock () from /lib64/libpthread.so.0 > > No symbol table info available. > > #3 0x00002b010d1720c0 in Init_iODBC () at henv.c:281 > > No locals. > > #4 0x00002b010d185f65 in SQLAllocHandle (handleType=30976, > inputHandle=0x0, outputHandlePtr=0x2aaaac08a798) at odbc3.c:251 > > retcode = <value optimized out> > > I will have a look at this issue and report back to you. Patrick ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ Iodbc-bugs mailing list Iod...@li... https://lists.sourceforge.net/lists/listinfo/iodbc-bugs CONFIDENTIAL. This e-mail and any attached files are confidential and should be destroyed and/or returned if you are not the intended and proper recipient. |