Re: [opendbx] /dev/urandom file descritpors left open, libopendbx-devel Digest, Vol 49, Issue 1

[Levine, A. <AL...@gl...>]

Norbert,

Let me first apologize for submitting a new e-mail each time I post as opposed to adding to the existing thread.
I have read-only capability on the web site, or I have not yet figured out how to add to a thread through the WEB site.
https://sourceforge.net/p/libopendbx/mailman/message/31896656/

It has been quite some time since I updated this thread, I wanted to be sure we had something pertinent to report.
We have found a couple work-arounds for our issues and have been running many hundreds to thousands of tests (tens of thousands of DB accesses) with very satisfactory results.
I would like to share with you these work-arounds as they may help future users of OpenDBX or you may have further comments for us.


1)       The file descriptors being left open seems to be related to the freeetds version specified in the  /etc/freetds/freeetd.conf file.  We were using tds_version = 8.0, when we go down to tds_version = 7.0 our open descriptor problems went away.  BTW, we also specify client charset = UTF-8 in the file.

2)      We were having major issues with the C++ API crashing the application when connection objects went out of scope:

a.      "if we call finish(), then when the function exits Result::~Result() crashes the application as seg fault on the delete m_impl statement"
We decided to abandon using the C++ API and switched over to using the C API calls within our C++ application.  This solved many issues we were having with the C++ objects.  I am not sure if it is our lack of understanding of the C++ usage, the C++ API in relation to freetds and/or MS SQL, or simply bugs within the C++ API.  Either way once we made this change things stabilized.

3)      We are calling into the library from multiple POSIX threads so we MUTEX'ed these calls to allow only one thread at a time accesses the library.  I do not think this is necessary as your documentation states it is thread-safe however we decided to do this as an extra precaution.

I appreciate your time and patience and want to thank you again for creating OpenDBX.

Regards,

Adam


____________________________________________________________
This e-mail (including attached documents) may contain confidential or proprietary
information intended only for use by the named recipient(s). Use by persons
other than the named recipient(s), further dissemination, or copying of this
email is prohibited unless authorized by the sender.