------=_NextPart_000_0032_01C5C28A.715A8400
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: 7bit

All -



I was wondering if I could get some assistance.



We have written a server that uses MySQL++ to connect to a MySQL database.
We are using connection pooling so when the server starts up we open up X
number of threads. Lately we are seeing connections close. We added the
ping() to verify that the connect still exists and reconnect if is does not.
This weekend we saw several ping requests fail. Is this normal? Should we
not use connection pooling? Any advice?



Craig




------=_NextPart_000_0032_01C5C28A.715A8400--

Craig Snyder wrote:
See the comments in the Wishlist regarding threading. Right now,
MySQL++ doesn't do anything at all to enforce the underlying
libmysqlclient restrictions on threads. It is quite possible,
therefore, that you are running into one of those limits.

It's also possible that you didn't build MySQL++ with threading support.
It isn't turned on by default.

The next version should have better constraints in place to help you
avoid violating libmysqlclient design limits. Would you be willing to
hammer such features and help us debug them or are you just looking for
a fix, and will move on after you get it?

--
MySQL++ Mailing List
For list archives: http://lists.mysql.com/plusplus
To unsubscribe: http://lists.mysql.com/plusplus?unsu...ie.nctu.edu.tw