Had this error msg in my application log:
[21/Feb/2002 10:16:20:7] info: REQ-012: thread add
[21/Feb/2002 10:16:20:7] info: REQ-012: thread add
[21/Feb/2002 10:16:20:7] info: ENGINE-ready: ready: 10820
BASEURL: https://ssunp03.company.com:8081
strURL: https://ssunp03.company.com:8081/ cgi-bin/gx.cgi/AppLogic+ EventServerManager
EventServerHttpInvocation > java.net.MalformedURLException: unknown protocol: https
**Out of memory, exiting**
ld.so.1: /pimcreg5/imc/nas/40sp3/nas/usr/java/bin/sparc/native_threads/jre: fatal: /pimcreg5/imc/nas/40sp3/nas/us
r/java/lib/sparc/native_threads/libjava.so: mprotect failed: Resource temporarily unavailable
Killed
Connected to LDAP server on ssunp03.company.com port 1390
[21/Feb/2002 02:42:49:1] info: ENGINE-class_loader_created: New class loader com.kivasoft.engine.EngineClassLoade
rNonVersionable@1c14d67f has just been created

Can anyone share with me his experience about ld.so.1?? What is it and why does it cause my apps server to reboot?

ld.so.1 is what Sun calls their dynamic loader. Are you running on a Sun? Anyway the dynamic loader has a man page..just type "man ld.so.1".

The "out of memory" error seems to be an earlier message. That may be closer to the cause. If your process was out of memory the dymanic loader isn't going to be able to attach shared libraries.

And the first error message I see complains about https being an unknown protocol. https is secure http, maybe your program doesn't handle it?

Anyway a dynamic loader problem can certainly cause a program to exit. But I doubt that it would cause a box to reboot. You may have rebooted coincidentally for some other reason.