java.net.SocketTimeoutException: Read Timed out

by **justinl** on Tue Jul 18, 2006 5:29 pm

I got this error when I was trying to test a transformation:

Error on server: ; nested exception is:
java.net.SocketTimeoutException: Read Timed out

Does Jitterbit have a length to the amount of fields I can transform? Is this something that I need to change?

My test source files is rather long and I tried a short (read: less rows) version and it seemed to work.

The rest of the error message (tracking) is below.

org.jitterbit.integration.server.IntegrationServerException: Error on server: ; nested exception is:
java.net.SocketTimeoutException: Read timed out
at org.jitterbit.integration.server.implementation.webservice.interchange.treemapper.impl.TreeMapperInfoProviderWsImpl.loadSourceDataTree(Unknown Source)
at org.jitterbit.integration.ui.interchange.entity.transformation.tree.LoadSourceDataJob$1.run(Unknown Source)
at org.jitterbit.integration.ui.core.DefaultUiWorker$RunnableWrapper.run(Unknown Source)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: java.net.SocketTimeoutException: Read timed out
at org.apache.axis.AxisFault.makeFault(AxisFault.java:101)
at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:146)
at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
at org.apache.axis.client.Call.invokeEngine(Call.java:2765)
at org.apache.axis.client.Call.invoke(Call.java:2748)
at org.apache.axis.client.Call.invoke(Call.java:2424)
at org.apache.axis.client.Call.invoke(Call.java:2347)
at org.apache.axis.client.Call.invoke(Call.java:1804)
at org.jitterbit.integration.server.implementation.webservice.interchange.treemapper.client.Konga_treemapper_infoproviderSoapBindingStub.loadSourceDataTree(Unknown Source)
... 9 more
Caused by: java.net.SocketTimeoutExcep

by **Torgil Zethson** on Tue Jul 18, 2006 6:15 pm

When you do a Test Transformation, the client sends a request to the Jitterbit server, and then waits for the server to send back the result of the test. If this takes too long, the call will time out, which is what you are experiencing.

Currently, the timeout is hardcoded, so there is unfortunately no way to increase it (other than rebuilding the client). We will look into the effort it would take to make this property configurable - let me get back to you on that.

The next question is why the test takes so long. The current value of the timeout is 10 minutes (I think), which is usually sufficient. Are you transforming very large amounts of data? Can you perhaps run the test with a smaller subset of your source data and see if the problem disappears?

Cheers,
- Torgil

by **justinl** on Tue Jul 18, 2006 6:20 pm

Torgil Zethson wrote:When you do a Test Transformation, the client sends a request to the Jitterbit server, and then waits for the server to send back the result of the test. If this takes too long, the call will time out, which is what you are experiencing.

Currently, the timeout is hardcoded, so there is unfortunately no way to increase it (other than rebuilding the client). We will look into the effort it would take to make this property configurable - let me get back to you on that.

The next question is why the test takes so long. The current value of the timeout is 10 minutes (I think), which is usually sufficient. Are you transforming very large amounts of data?

Cheers,
- Torgil

The text file itself is only 194KB, but each row can have up to 256 mappings to a field within the source file. I don't know if that will slow down things.

I am running my JitterBit Client and Server on my laptop (1.6 GHz 1 GB RAM). But it doesn't time out after 10 minutes... it looks like it timesout at 5-7 minutes... but I could be wrong.

by **Torgil Zethson** on Tue Jul 18, 2006 6:21 pm

Another alternative, if you want to make sure that the transformation is actually running ok, is to create an Operation from your transformation, and then run that operation on the server by selecting "Run Operation" from the "Actions" menu (or by clicking on the flash-button in the Operation page). When you do that the operation will run on the server without the client waiting for it to complete, so you will not have any timeout issues. Check the Operation Log periodically (click on the Operation Log button in the Operation page toolbar, it's right next to the Run Operation button) until the operation completes.

by **Torgil Zethson** on Tue Jul 18, 2006 6:27 pm

The text file itself is only 194KB, but each row can have up to 256 mappings to a field within the source file. I don't know if that will slow down things.

Generally, the more mappings you have, the longer the transformation will take, and 256 mappings is quite a lot. Can you try to reduce the source file to one single row, and see what happens?

If possible, can you post a Jitterpak with your project here, including some sample source data? Then we could debug it and see what is going on.