Re: [Sqlrelay-discussion] Glibc error with Java API

[Rodrigo P. T. <te...@de...>]

Hi David,

Thanks for your answer!
By the way we solved the problem. Looks like the problem is happening
because
we are using an static connection between our Java APP and SQLRelay or
so the
Java APP reuses the same SQLRelay connection each time (running as a daem=
on)
it needs to connect to DB backend and the connection is never closed
(destroyed).
We change our Java APP to close/destroy the connection to SQLRelay after
each
task (some SQL queries) and the problem disappeared completely!

The problem is happening (using an static connection) with any kind of
queries but
just to give you examples:

Query 1:
SELECT RadAcctId, AcctSessionId, AcctUniqueId, UserName, Realm,
NASIPAddress, NASPortId, NASPortType, AcctStartTime, Acct
StopTime, AcctSessionTime, AcctAuthentic, ConnectInfo_start,
ConnectInfo_stop, AcctInputOctets, AcctOutputOctets, CalledStationId,
CallingStationId, AcctTerminateCause, ServiceType, FramedProtocol,
FramedIPAddress, AcctStartDelay, AcctStopDelay FROM radacct WHERE
AcctSessionId=3D'c5d10af3-cfb8f381@192.168.1.100' AND ConnectInfo_start =3D=

'1e0744b4f44da09o1' AND ConnectInfo_stop =3D 'as2ccc0688' AND
AcctTerminateCause =3D '200'

Query 2:
Update acc_relay set status =3D '0' where id =3D 10


Thanks for your prompt help!

Telles


David Muse wrote:
> I think I remember someone reporting this before, maybe you :)
>
> Those errors generally occur when there's a double free or an
> uninitialized variable.  I'll look through the code for something like
> that, but if you can narrow down which queries cause the crash, it'll b=
e
> a lot easier to figure out.
>
> Dave
> dav...@fi...
>
>
> On Mon, 2006-07-24 at 16:19 -0300, Rodrigo P. Telles wrote:
>  =20
>> Hi Folks,
>>
>> I'm facing some errors using SQLRelay 0.36.4 with Java API as listed b=
elow.
>> I tried to update to the latest SQLRelay version (0.37) but nothing ch=
anges the error still happening.
>> When that error happens the Java App is killed!
>>
>> 2006-07-24 15:31:57.535476500 *** glibc detected *** free(): invalid
>> next size (fast): 0x08069680 ***
>>
>> 2006-07-24 15:20:53.190113500 *** glibc detected *** free(): invalid
>> next size (fast): 0x0806e300 ***
>>
>> 2006-07-24 15:19:07.109816500 *** glibc detected *** free(): invalid
>> next size (fast): 0x080b5f18 ***
>>
>> 2006-07-24 14:55:28.414175500 *** glibc detected *** free(): invalid
>> next size (fast): 0x08105270 ***
>>
>> 2006-07-24 14:53:42.518603500 *** glibc detected *** free(): invalid
>> next size (fast): 0x08106058 ***
>>
>> 2006-07-24 14:53:12.011833500 *** glibc detected *** free(): invalid
>> pointer: 0x08133558 ***
>>
>> 2006-07-24 14:51:10.687502500 *** glibc detected *** malloc(): memory
>> corruption: 0x08128c28 ***
>>
>> 2006-07-24 14:50:25.076671500 *** glibc detected *** free(): invalid
>> next size (fast): 0x080f5738 ***
>>
>> 2006-07-24 14:48:39.040298500 *** glibc detected *** free(): invalid
>> pointer: 0x08133468 ***
>>
>> 2006-07-24 14:47:53.374118500 *** glibc detected *** free(): invalid
>> next size (fast): 0x08139610 ***
>>
>> 2006-07-24 14:47:07.763850500 *** glibc detected *** free(): invalid
>> pointer: 0x08167e98 ***
>>
>> 2006-07-24 14:44:21.419332500 *** glibc detected *** free(): invalid
>> next size (fast): 0x08128440 ***
>>
>> 2006-07-24 14:43:20.713662500 *** glibc detected *** corrupted
>> double-linked list: 0x08139608 ***
>>
>> 2006-07-24 14:37:17.769239500 *** glibc detected *** free(): invalid
>> next size (fast): 0x0806bef0 ***
>>
>> 2006-07-24 14:29:14.538502500 *** glibc detected *** free(): invalid
>> next size (fast): 0x080f8918 ***
>>
>>
>> Its happening on some (random) SGBD operations (select, update, delete=
, etc).
>>
>> Informations about O.S.:
>> Mandriva 2006 Kernel 2.6.12-12mdk
>> glibc-2.3.5-5mdk
>> gcc-4.0.1-5mdk
>> gcc-c++-4.0.1-5mdk
>>
>> Looks like there is some memory leak on SQLRelay.
>> Thanks for any help!
>>
>> Telles
>>
>>    =20