[xgws-dev] XSUL httpserver crashes

[Aleksander Slominski]

Sune Kristensen wrote:

> Sune Kristensen wrote:
>
>> Aleksander Slominski wrote:
>>
>>> Sune Kristensen wrote:
>>>
>>>> I have just startet to use XSUL, and I have a server up and running 
>>>> that can deliver the WSDL file.
>>>> If I go to http://localhost/Session?wsdl and refresh rapidly the 
>>>> jvm crashes (tested with java 1.4.2_06 and 1.5.0_02).
>>>> The server is running on Linux (SuSE 9.2, kernel 2.6.8).
>>>> The WSDL file is rather large (2051 lines).
>>>>
>>>> Don't know if the error is in the jvm or in XSUL, but though I 
>>>> would try here first!
>>>
>>>
>>> hi Sune,
>>>
>>> thanks for reporting the problem - i have not seen ti before. based 
>>> on stack trace server tries to write response to client (browser) 
>>> and it fails maybe because client already closed socket and is 
>>> opening another connection to server.
>>>
>>> could you check if you do not have an environment prone to  *Bug 
>>> ID:* 4630104 ?
>>>
>>> http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4630104
>>
>> Have nss_ldap, but it is a version where the problem should be fixed.
>>
>>>
>>> first thing try preloaading libjsig.so:
>>>
>>> export LD_PRELOAD=/pack/jdk1.4.2_06/jre/lib/i386/libjsig.so
>>
>> When this export is run, everything works as it should, thanks :-)
>>
>>> and then look how nss_ldap (http://www.padl.com/OSS/nss_ldap.html) 
>>> is installed on this system
>>>
>>> possibly related though it should have been fixed in  1.4.2_06:
>>>
>>> http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=5101391
>>
>> This could also be the problem, except I still get the error in 
>> 1.5.0_02, will report it to Sun!
>>
>>> let me know about your progress - if i could reproduce it i would 
>>> try to put some workarounds - it is not good to *crash* JVM by 
>>> reading WSDL in browser ...
>>>
>>> thanks,
>>>
>>> alek
>>
>> Thanks for the help
>>
>> Sune
>>
>> _______________________________________________
>> xgws-dev mailing list
>> xgws-dev_at_cs.indiana.edu
>> http://mailman.cs.indiana.edu/mailman/listinfo/xgws-dev
>
> I have just updated my nss_ldap from 215 to 238, and now it looks like 
> it is working, so the problem should be solved :-)
>
> Thanks againg for the help
>
i am very glad to hear that the problem is easy to fix and probably will 
be of less importance in future (when everybody uses new nss_ldap).

alek

-- 
The best way to predict the future is to invent it - Alan Kay