Native Connector

users
#1

Well, that autoReconnect=true must have something to do with JAVA
...

            I 'searched' and uncovered nearly 100,000 articles [whew :wink:
]

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

#2

Thanks a lot, Girvin...
My situation is exactly as you describe it. I used to run my own server,
installing everything from Linux to Apache2, PHP, mail, MySQL, etc.
Therefore I had the possibility to set my OWN parameters for MySQL.
For cost and other reasons I changed to a "stripped-down" web-hosting
structure and therefore have stopped being my own admin....
I also think that 60 seconds is an inappropriate value for the wait_timeout
because it doesn't even allow you to go have a quick coffee (or other, more
pressing things...).
Yes, in MY situation it would be great if the native connector supported
a kind of automatic reconnect after the SERVER (nothing to do with LO-Base!)
shuts down an idle connection (in my case in 60 seconds, even though 28800
would be allowed!!!
Regards from Austria
H. S.

#3

Heinrich,
Although I do not have the problem you are experiencing, I am keeping an eye on this thread is case I do have a similar problem in the future. I hope you can get an answer soon to solve your immediate problem. Aside from your cup of coffee example, from my experience, the Base Report Generator can take much more than 60 seconds to render a large report. I am not sure how Base collects the data for a report, but if it does so a record at a time, then your server would time out way before the report is finished! I would think that the best case would be that the constant reconnects would slow the Report Generator even more.

Since it sounds like your system worked before LO 4.2.x and I suspect you where using the Oracle MySQL-connector-java, as I am, there may be a way to replace the new native connector with the "tried-and-true" Oracle connector. That would get you up and running again until more information on the native connector is released. I have no experience with this, but it may be an option for you, if it can be done.

Good luck.
Girvin