[Geoserver-users] glibc error

Hi
since few days I get strange errors like:


SELECT encode(asBinary(force_2d(“wkb_geometry”),‘XDR’),‘base64’)
*** glibc detected *** free(): invalid pointer: 0x08274410 ***
03.03.2008 20:10:25 org.apache.catalina.core.AprLifecycleListener lifecycleEvent

or


traverseXlinkExpiry = null
Result:
*** glibc detected *** double free or corruption (!prev): 0x082887c8 ***
05.03.2008 13:48:27 org.apache.catalina.core.AprLifecycleListener lifecycleEvent

I cannot reproduce it, it happens from time to time. It kills the JVM and I have to start tomcat again. It happens with 1.6rc3 and 1.6.1 but was running perfect with rc3 so there shouldn’t be something wrong with geoserver but with our server. Any ideas?

Mit freundlichem Gruss
Stefan Ziegler
Leiter Aufsicht

Kanton Solothurn
Bau- und Justizdepartement
Amt für Geoinformation
Rötistrasse 4
4501 Solothurn
Telefon 032 627 75 96
Telefax 032 627 75 98
stefan.ziegler@anonymised.com
http://www.so.ch

Ziegler Stefan ha scritto:

Hi
since few days I get strange errors like:

....
SELECT encode(asBinary(force_2d("wkb_geometry"),'XDR'),'base64')
*** glibc detected *** free(): invalid pointer: 0x08274410 ***
03.03.2008 20:10:25 org.apache.catalina.core.AprLifecycleListener lifecycleEvent
....

or

....
traverseXlinkExpiry = null
Result:
*** glibc detected *** double free or corruption (!prev): 0x082887c8 ***
05.03.2008 13:48:27 org.apache.catalina.core.AprLifecycleListener lifecycleEvent
.....

I cannot reproduce it, it happens from time to time. It kills the JVM and I have to start tomcat again. It happens with 1.6rc3 and 1.6.1 but was running perfect with rc3 so there shouldn't be something wrong with geoserver but with our server. Any ideas?

Well, the error is obviously occurring in Tomcat, did you install the
APR runtime?
Moreover, I know that glibc became picky on free() and now checks
if the area to be freed is actually allocated or not, while
it wasn't doing that before. This kills quite a bit of native code
in the standard java runtime too.
Try adding the following line in the script that starts up Tomcat:
export MALLOC_CHECK_=0

This should make glibc behave like before
Let me know if this is of any help
Cheers
Andrea