Native Connector

users
#1

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 :wink:

       If the 2nd - I'll be awaiting someone else's response on this list;
           and will attempt to figure out what's what :wink:

#2

Hello,
I am NOT referring to the server-side machine shutting down but - as I
mentioned already earlier - to the MySQL-Server-parameter "wait_timeout"
which is specified in my.cnf. It simply defines the interval of "no request"
from a particular client to the server it is connected to. The server shuts
down the connection if that period has expired without further hearing
from the client. My problem is that I am NOT the system administrator
of the server and the sysadmin of the server won't increase that
wait_timeout value. JDBC has a way around this by auto-reconnecting the
client if this is specified when establishing the connection. This is
NOT an ideal situation (re-establishing the connection takes time...) but
it is certainly better than having to shutdown/restart LO...
Regards
H. S.

#3

Hi :slight_smile:
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 :slight_smile:

#4

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

#5

Hello Girvin,
Yes, I will keep on using the JDBC-Driver, hoping that the native connector
will support autoreconnect some time in the future. If LO drops JDBC, I
have to look for a different Office system. To suggest restarting LO every time
after having to go away for a short break really is NOT feasible in reality.
Regards
Heinrich
P.S.: What do you guys think of Conchita winning the Eurovision song contest --
but THAT certainly should NOT start a new thread...(smiley!)