Strange mapscriptJNI_delete_1layerObj+0xf error killing Tomcat

[Rodrigo Del C. Andrade]

    Thanks a lot for all the replies, folks! I really appreciate it.
    I am about to get to work on that, so I will first dl and compile 
the svn version and give it a go without any further modifications, 
(like delete(), but I gotta say I am kinda of relieved: its a LOT of 
stuff to delete). It will be sort of a pain to test it because it is 
only crashing on the server, but w/e.
    Tamas: thanks too for the tip. Indeed all object creations we have 
in the code go with the new obj(parent) constructor. I will see how it 
works with the svn version and if it doesn't work I will implement that.

    Best regards,

    Rodrigo


    --

*Rodrigo Del C. Andrade*
/Programador/
/SIC - SSE - Soluções Segurança Pública/

*DÍGITRO TECNOLOGIA*
*E-mail:* rodrigo.andrade at digitro.com.br 
<mailto:rodrigo.andrade at digitro.com.br>
*Fone:* +55 48 3281-7314 / +55 48 3281-7000
*Fax:* +55 48 3281-7299
*Site:* www.digitro.com <http://www.digitro.com>


Umberto Nicoletti wrote:
> 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
>>  > #
>>  >
>>