Well, that autoReconnect=true must have something to do with JAVA
...
I 'searched' and uncovered nearly 100,000 articles [whew
;-)
]
https://www.google.com/search?q=autoReconnect%3Dtrue&ie=utf-8&oe=utf-8&aq=t&rls=org.mozilla:en-US:official&client=firefox-a&channel=sb
BTW - when opening up the first few, I noticed others are
asking the
same question re. this timing out ???!!!???!!!???
Oops - Something tells me I should quit calling this machine a
glorified-typewriter; maybe it will want revenge and blow up ... ... ...
my mouse already died this year; had to replace the li'l
fella' ;-)
From: Girvin Herr <girvin.herr@sbcglobal.net>
Date: Sun, May 11, 2014 at 2:53 PM
Subject: Re: [libreoffice-users] Native Connector
To: users@global.libreoffice.org
Yes, if I understand Mr. Stoellinger's problem correctly, it is the
MySQL
server (aka "back-end") which is dropping his connection. According
to my
MySQL documentation, by default, the MySQL server drops any connection
after 8 hours of continuous connection. However, Mr. Stoellinger's admin
has reduced that time to 60 seconds! IMHO, that is ridiculous, but
it must
be the policy at his institution, so he must live with it. The MySQL
connector driver that he has been using has a workaround by triggering a
reconnect operation every so often, effectively restarting the 60-second
timer. That is the purpose of the "autoReconnect=true" connector driver
parameter he talks about. Now, it appears that the new LO Base has a
MySQL
native driver that replaces the Oracle MySQL-connector-java driver
that he
most likely has been using and he needs to know if the new LO native
driver
supports the reconnect schema and if so, how to implement it. As far
as I
know, no one on this list so far has given him the answer to that
question.
I have no experience with the new native driver (yet), so I do not have
the answer. If the native driver does not support it, or he does not
get
an answer, I would suggest keeping the Oracle JDBC driver until he
gets his
answer, if the new LO still allows replacement of the native built-in
driver.
BTW: I am my own admin, so my MySQL server is still set to the default
timeout, if any. Therefore, I do not experience this disconnect
problem.
However, every so often, I see a posting about it on this forum, so
he is
not alone.
HTH.
Girvin Herr
On 05/10/2014 03:37 PM, Tom Davies wrote:
Hi :)
It's the 2nd one Anne-ology.
The connector is some sort of bridge between Base and MySql. It's the
bridge that is timing out rather than the computer afaik.
Regards from
Tom :)
On 10 May 2014 22:13, anne-ology <laginnis@gmail.com> wrote:
If you're referring to the computer-machine shutting down
and/or
entering sleep-mode, then there's a simple solution;
if you're referring to something else - well, I haven't a
clue.
If the 1st - go to properties/options/ and re-set the timing
mechanism to never shut down;
you can also do similarly in various programs - as LO -
which otherwise decide they want to save every so often,
causing
me to lose my train of thought while writing ;-)
If the 2nd - I'll be awaiting someone else's response on this
list;
and will attempt to figure out what's what ;-)
From: Heinrich Stoellinger <hc.stoellinger@aon.at>
Date: Sat, May 10, 2014 at 8:08 AM
Subject: [libreoffice-users] Native Connector
To: "users@global.libreoffice.org" <users@global.libreoffice.org>
Hello,
It's good to see a native connector for MySQL under 4.2.
One question: In the server my.cnf the value for wait_timeout
is set to 60 seconds and will not be increased. This is a nuisance
if one needs to be connected over longer periods but sometimes
has to go away from there client for more than a minute.
Under the JDBC-connector there is a possibility to specify
"?auto-reconnect=true" after the database name.
Is there some facility like that under the native connector?
Regards
H. Stoellinger
--
Erstellt mit Operas revolutionärem E-Mail-Modul:
http://www.opera.com/mail/