------_=_NextPart_001_01C6E0A8.61FF8F86
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

When there is a problem with a connection the next time we call a
function like mysql_query() or mysql_ping() it does report an error
witch is fine but if I call

2 function in a row before reseting the connection the function crash
instead of reporting an error, I can leave with that.

=20

Now when a connection is left idle for some time and is probably
disconnect if I call mysql_query() it does crash instead of reporting an
error.

=20

How can I validate this properly or handle it correctly?


------_=_NextPart_001_01C6E0A8.61FF8F86--

------_=_NextPart_001_01C6E0A9.05D6D7FE
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Looking at may trace, here is what is happening internally in the API:

=20

free_old_query

mysql_close

mysql_close

mysql_reconnect

mysql_send_query

mysql_real_query

mysql_query

=20

_____ =20

From: Julien Chavanton=20
Sent: September 25, 2006 9:42 AM
To: 'plusplus (AT) lists (DOT) mysql.com'
Subject: Aparent connection lost resulting in crash

=20

When there is a problem with a connection the next time we call a
function like mysql_query() or mysql_ping() it does report an error
witch is fine but if I call

2 function in a row before reseting the connection the function crash
instead of reporting an error, I can live with that.

=20

Now when a connection is left idle for some time and is probably
disconnect if I call mysql_query() it does crash instead of reporting an
error.

=20

How can I validate this properly or handle it correctly?


------_=_NextPart_001_01C6E0A9.05D6D7FE--

Hi Julien,

I think the questions you're asking are MySql issues, and should
probably be taken up on a mailing list for the C API there. This mailing
list is for issues specific to the MySQL++ wrapper library.

Regards,

Matt.


-----Original Message-----
From: Julien Chavanton [mailto:jc (AT) atlastelecom (DOT) com]
Sent: 25 September 2006 14:42
To: plusplus (AT) lists (DOT) mysql.com
Subject: Aparent connection lost resulting in crash

When there is a problem with a connection the next time we call a function
like mysql_query() or mysql_ping() it does report an error witch is fine but
if I call

2 function in a row before reseting the connection the function crash
instead of reporting an error, I can leave with that.



Now when a connection is left idle for some time and is probably disconnect
if I call mysql_query() it does crash instead of reporting an error.



How can I validate this properly or handle it correctly?



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

Thank you, I do not find the C API mailing list in
http://lists.mysql.com/

Also the same "problem" exists while using Mysql++ how shall we deal
with connection lost exactly?





-----Original Message-----
From: Matt Dargavel [mailto:matt (AT) shout-telecoms (DOT) com]=20
Sent: September 25, 2006 10:13 AM
To: plusplus (AT) lists (DOT) mysql.com
Subject: RE: Aparent connection lost resulting in crash


Hi Julien,

I think the questions you're asking are MySql issues, and should
probably be taken up on a mailing list for the C API there. This
mailing
list is for issues specific to the MySQL++ wrapper library.

Regards,

Matt.


-----Original Message-----
From: Julien Chavanton [mailto:jc (AT) atlastelecom (DOT) com]=20
Sent: 25 September 2006 14:42
To: plusplus (AT) lists (DOT) mysql.com
Subject: Aparent connection lost resulting in crash

When there is a problem with a connection the next time we call a
function
like mysql_query() or mysql_ping() it does report an error witch is fine
but
if I call

2 function in a row before reseting the connection the function crash
instead of reporting an error, I can leave with that.

=20

Now when a connection is left idle for some time and is probably
disconnect
if I call mysql_query() it does crash instead of reporting an error.

=20

How can I validate this properly or handle it correctly?



--=20
MySQL++ Mailing List
For list archives: http://lists.mysql.com/plusplus
To unsubscribe:
http://lists.mysql.com/plusplus?unsu...ecom (DOT) com


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

Julien Chavanton wrote:
There is no separate list. C API issues are handled on the main MySQL list.

Presumably you're using 5.0, which apparently has a feature to drop idle
connections. (This question has been coming up a lot lately....) If
so, turn on the connection retry option. Search the list...it's come up
twice recently.

I don't know how the library could deal with this any better than it
already does. That's not to say that it's nice...it's just that a
network connection failure is a pretty serious thing. MySQL++ itself
doesn't have the knowledge to do anything more than just ask the C API
to retry the connection, and throwing an exception is probably
excessive. Ideas solicited.

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