Administration Guide › Troubleshooting › General Troubleshooting › Data Replication Suddenly Stops When Using ADSL

Data Replication Suddenly Stops When Using ADSL

Symptom:

If a CA DataMinder machine is connected to its parent server using ADSL (Asymmetric Digital Subscriber Line), data replication can suddenly stop because of a lost connection even though ADSL is 'always on'.

Reason:

Under certain network conditions, a broken remote procedure call between CA DataMinder machines can trigger a communication timeout. Because the default timeout can be lengthy (hours, rather than seconds), it can appear as though replication has been permanently lost.

Solution:

If communication resumes between the machines, data replication resumes automatically when the timeout expires. But for usability purposes, you may want to configure a shorter timeout:

1. On both the CA DataMinder machines, go to the CA DataMinder installation.
2. In the \System subfolder locate (or create) the file, JVM.Properties.
3. Add the following line to this file:

   jvm.define1=sun.rmi.transport.tcp.readTimeout=120000
   

   This resets the ADSL timeout to two minutes (that is, 120,000 milliseconds), so eliminating the perception that replication has stopped completely.

4. On both machines, restart the CA DataMinder service.