Strange mapscriptJNI_delete_1layerObj+0xf error killing Tomcat

[Benedikt Rothe]

Hi

Some developers (Umberto, Tamas) work on a solution of this problem. 

As a workaround I made good experiences with 
http://lists.umn.edu/cgi-bin/wa?A2=ind0506&L=mapserver-users&P=87500

> if we dynamically create mapserver-objects, we allway use code like 
this:
> classObj cO = new classObj(...);
> ..
> // Do something with cO
> ..
> //now cO isn't used any more
> cO.delete()

With "freeing manually" we made the Mapserver inside Tomcat quite stable.
Hope, this helps
Benedikt


UMN MapServer Users List <MAPSERVER-USERS at LISTS.UMN.EDU> schrieb am 
31.05.2007 15:13:41:

> 
>     Hello dear list.
> 
>    A problem is happening in our production machine which we were 
> unable to reproduce on our development machines. We have a very 
> large application almost ready for deployment, in which one of the 
> modules is written in java mapscript 4.10.1,  and the error on the 
> attached log happened for the first time when we installed the 
> application on the production server. Whats worse, the GIS module 
> causing the error brings down Tomcat and the whole application with it.
>     This is a excerpt from the JVM log:
> 
> # An unexpected error has been detected by HotSpot Virtual Machine:
> #
> #  SIGSEGV (0xb) at pc=0x636ff93b, pid=19162, tid=1759710128
> #
> # Java VM: Java HotSpot(TM) Server VM (1.5.0_07-b03 mixed mode)
> # Problematic frame:
> # C  [libmapscript.so+0x3893b] 
> Java_edu_umn_gis_mapscript_mapscriptJNI_delete_1layerObj+0xf
> #
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/mapserver-users/attachments/20070601/d1fa4e7e/attachment.htm>