SocketWrite0 Hotspot crashes occur on Engines

SocketWrite0 Hotspot crashes occur on Engines

book

Article ID: KB0086679

calendar_today

Updated On:

Products Versions
TIBCO DataSynapse GridServer -
Not Applicable -

Description

Resolution:
There is a JVM bug which may cause socketWrite0 Hot Spot crashes on Engines on Red Hat Advance Server 2.1 systems. See below for an example hs_err* file. This bug is documented at http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4630104.
To work around this issue, load libjsig.so before you run the engine.sh script by setting the LD_PRELOAD environment variable. For example, you can add it to the engine.sh script with LD_PRELOAD=/path/to/DSEngine/jre/lib/i386/libjsig.so. Another alternative is to set it in the Environment Variables field of the Engine Configuration page, although it should be noted that the Environment Variables field is ignored when using Grid Libraries.
If you use a relative path, such as LD_PRELOAD=./jre/lib/i386/libjsig.so, then command services will fail, since they do not run from the base Engine directory but run from their own temporary directory. To avoid this, use an absolute path.
Note that if you do load libjsig.so, this will cause PDriver to return non-zero exit codes on executed commands or back-ticked commands, even if the command executed successfully.
Hotspot stack follows:
Unexpected Signal : 11 occurred at PC=0x405608C3
Function=JVM_handle_linux_signal+0x93
Library=./jre/lib/i386/server/libjvm.so
Current Java thread:
at java.net.SocketOutputStream.socketWrite0(Native Method)
at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
at java.net.SocketOutputStream.write(SocketOutputStream.java:124)
at HTTPClient.HttpOutputStream.write(HttpOutputStream.java:333)
- locked &lt0x44f11bb8> (a HTTPClient.HttpOutputStream)
at java.io.OutputStream.write(OutputStream.java:58)
at com.livecluster.xml.XmlObjectOutputStream.writeHeader(XmlObjectOutputStream.java:17)

Issue/Introduction

SocketWrite0 Hotspot crashes occur on Engines