Netsuite - Read time out error after Sep 16, 2015 release

Document created by ruchika_yadav Employee on Sep 17, 2015Last modified by dave_lesshafft on Mar 2, 2016
Version 2Show Document
  • View in full screen mode
After the 16 September 2015 release , you might see these errors in the process reporting when you are using the netsuite connector shape.

 

"ERROR: Error executing Netsuite operation: ; nested exception is: java.net.SocketTimeoutException: Read timed out"
Here are the steps to fix the issue: http://help.boomi.com/atomsphere/GUID-D01124FB-B841-4F8F-93E2-E5EF113F195D.html

 

If you have your own Atom, Molecule or Atom Cloud, and if you use connectors that use the HTTP transport, you can adjust these network timeout settings used by these connectors. The -Dsun.net.client.defaultConnectTimeout property sets the timeout period to establish an HTTP client connection. The -Dsun.net.client.defaultReadTimeout property sets the timeout period for an individual attempt to read data from an established HTTP client connection.

 

The default value for each property is 120000 milliseconds. You should increase the setting if the HTTP endpoints take longer than two minutes to return a response.
  1. Stop the Atom or Molecule.
  2. Navigate to <atom_or_molecule_installation_directory>/bin.
  3. Open the atom.vmoptions file in a text editor such as Notepad.
    To change the timeout period for establishing an HTTP client connection, change the value for the following property:
   -Dsun.net.client.defaultConnectTimeout

 

   To change the timeout period for reading data from an HTTP client connection, change the value for the following property:
   -Dsun.net.client.defaultReadTimeout

 

     4. Save the file.
     5. Restart the Atom or Molecule.

Example: Change it a higher value
-Dsun.net.client.defaultConnectTimeout=1200000
-Dsun.net.client.defaultReadTimeout=1200000

2 people found this helpful

Attachments

    Outcomes