Strange mapscriptJNI_delete_1layerObj+0xf error killing Tomcat

[Oliver Wesp]

Hi everybody,

I just want thank everybody for the information in this thread. We're 
facing similar issues with java mapscript crashing the vm. Unfortunately 
  the application relies on the dynamic creation of layers and classes.

I tried the svn version this afternoon and it seems to be stable. No 
more tomcat crashes till now. I will do some more testing on monday but 
it looks like Umberto was right with expecting some good news :-)

Just in case this information is usefull: We're running our application 
on Solaris 8 using Shapefiles, GDAL Raster (HFA) and WMS as datasources. 
Tomcat is  5.0.28, JAVA is j2sdk1.4.2_11.

Regards,
Oliver



Umberto Nicoletti schrieb:
> I suggest against this practice (no pun intended Benedikt, I sincerely
> appreciate your help).
> I say let's wait until Rodrigo tries out a rfc-24 enabled build,
> frankly I am quite positive rfc-24 will fix his issues.
> 
> Regards,
> Umberto
> 
> On 6/1/07, Benedikt Rothe <umn-ms at hydrotec.de> wrote:
>>
>> 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
>>  > #
>>  >
>>
> 
> 
> 

-- 
Dipl.-Geogr. Oliver Wesp
GDV Gesellschaft für geografische Datenverarbeitung mbH
Binger Str. 49-51
55218 Ingelheim am Rhein
Germany
Fon 049(0)6132-7148-18
Fax 049(0)6132-7148-28
www.gdv.com
Sitz der Gesellschaft: Ingelheim
Amtsgericht Mainz HRB 23123
Gerichtsstand Mainz
Geschäftsführer: Thomas Riehl, Dirk Hübener