dhis2-devs team mailing list archive
-
dhis2-devs team
-
Mailing list archive
-
Message #06525
Re: Troubles with database communication
Hi Orvalho
Whereas I do agree postgres might solve your problems it does seem
like a drastic solution to this problem. The fact is mysql does
actually work and apparently work well so it should be possible to
solve this.
Trying to think logically here ... you have another similar setup
where everything seems ok. I suppose the load could be quite
different on the two servers, but lets discount that for a bit. If
you are reusing old stale and broken connections then the only three
places i can think to look are:
(i) the jdbc driver (version compatibility). I think you checked that.
(ii) tcp/ip problems
(iii) the connection pool
Regarding (ii) can you check the value of bind-address in
/etc/mysql/my.cnf (or whatever config file you are using). This
should be set to 127.0.0.1 unless you are connecting to the db from a
different host. At least this interface will always be up so you
shouldnt get intermittent network errors on it.
Regarding (iii) I suggest (as above) that you look at setting up c3p0
parameters to periodically test and discard stale connections. Does
anybody (maybe Indian team) have a good sample config?
Regards
Bob
On 4 July 2010 13:09, Orvalho Augusto <orvaquim@xxxxxxxxx> wrote:
> It will give some job because we developed a tool to convert data from one
> database to MySQL.
>
> It is the only thing I can try to do to solve.
>
> Caveman
>
>
>
> On Sun, Jul 4, 2010 at 8:16 AM, Knut Staring <knutst@xxxxxxxxx> wrote:
>>
>> Is postgres out of the question?
>>
>> On Jul 4, 2010 5:59 AM, "Orvalho Augusto" <orvaquim@xxxxxxxxx> wrote:
>>
>> I do not know what to do. I have found this:
>>
>> http://dev.mysql.com/doc/refman/5.1/en/connector-j-usagenotes-troubleshooting.html
>>
>> And what makes me feel really bad is:
>> "22.3.5.3.4: I have a servlet/application that works fine for a day, and
>> then stops working overnight MySQL closes connections after 8 hours of
>> inactivity. You either need to use a connection pool that handles stale
>> connections or use the "autoReconnect" parameter"
>>
>> and
>> "The autoReconnect facility is deprecated, and may be removed in a future
>> release. "
>>
>>
>> So what we do?
>>
>> Caveman
>>
>> On Mon, Jun 28, 2010 at 12:59 PM, Bob Jolliffe <bobjolliffe@xxxxxxxxx>
>> wrote: > > Hi > > It looks...
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~dhis2-devs
>> Post to : dhis2-devs@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~dhis2-devs
>> More help : https://help.launchpad.net/ListHelp
>>
>
>
>
>
Follow ups
References
-
Troubles with database communication
From: Orvalho Augusto, 2010-06-23
-
Re: Troubles with database communication
From: Jason Pickering, 2010-06-23
-
Re: Troubles with database communication
From: Bob Jolliffe, 2010-06-23
-
Re: Troubles with database communication
From: Orvalho Augusto, 2010-06-23
-
Re: Troubles with database communication
From: Bob Jolliffe, 2010-06-23
-
Re: Troubles with database communication
From: Orvalho Augusto, 2010-06-24
-
Re: Troubles with database communication
From: Bob Jolliffe, 2010-06-24
-
Re: Troubles with database communication
From: Orvalho Augusto, 2010-06-28
-
Re: Troubles with database communication
From: Bob Jolliffe, 2010-06-28
-
Re: Troubles with database communication
From: Orvalho Augusto, 2010-07-04
-
Re: Troubles with database communication
From: Knut Staring, 2010-07-04
-
Re: Troubles with database communication
From: Orvalho Augusto, 2010-07-04