Troubleshooting
Problem
Encounter timeout error when processing a large file using IBM WebSphere® Transformation Extender (WTX) 8.x with the RMI Server.
Symptom
The following error is encountered
java.net.SocketTimeoutException: Read timed out
Stack trace :
0000005e SystemErr R Caused by: java.net.
SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:155)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:229)
at java.io.BufferedInputStream.read(BufferedInputStream.java:246)
at java.io.DataInputStream.readByte(DataInputStream.java:267)
at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:
205)
at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:141)
at com.ibm.websphere.dtx.dtxpi.rmi.IMMapImpl_Stub.run(IMMapImpl_Stub.
java:539)
at com.ibp.epp.wtx.WTXUtils.runMap(WTXUtils.java:365)
at com.ibp.prcctrlasync.utils.CtrlAsyncSCTUtils.runMapHabilitation
(CtrlAsyncSCTUtils.java:78)
Cause
When using WTX to transform large files using the RMI Server, if processing requires a time longer than the default RMI timeout a timeout error is encountered and processing fails.
Environment
When using WTX to transform large files using the RMI Server, if processing requires a time longer than the default RMI timeout a timeout error is encountered and processing fails.
Diagnosing The Problem
Error 'java.net.SocketTimeoutException: Read timed out' is contained within the RMI server log when processing a large file using IBM WebSphere Transformation Extender 8.x with the RMI server.
Resolving The Problem
Set the parameter rmi.client.timeout
java -Drmi.client.timeout=60 <classname> represents existing command tokens for the program.
-Drmi.client.timeout=60. This should set to be the same.
The value of 60 is just an example.
-D specifies the command token for Java.
Product Synonym
Ascential Datastage TX Mercator
Was this topic helpful?
Document Information
Modified date:
16 June 2018
UID
swg21461419