Istool command fails with "java.net.SocketTimeoutException: Read timed out"

-

Problem(Abstract)

Istool command fails with "java.net.SocketTimeoutException: Read timed out"

Symptom

Command:

/opt/IBM/InformationServer/Clients/istools/cli/istool.sh export
-domain UHQTETL02:9445 -authfile '/home/BICCBLD/.ds_auth' -ar export-uhqtetl01-20150720.isx -up -ds '-incdep "UHQTETL01/BICC_DEV/Jobs/*/*.*"' –verbose

Beginning Export
Export failed: Read timed out; nested exception is:
java.net.SocketTimeoutException: Read timed out


Cause

Some import operations take longer than the 10 minute default client timeout setting.

Resolving the problem

To resolve this issue, do the following:

1) Log in to the Engine server where the istool command is executed from
2) Go to .../ASBNode/eclipse/plugins/com.ibm.iis.client/
3) Do a vi on iis.client.site.properties file
4) Locate "com.ibm.iis.http.soTimeout" entry. If it not present, then
create it at the bottom of the page and set it to 10800000 (3 hours) -
"com.ibm.iis.http.soTimeout=10800000"
5) Make sure you don't have any backup iis.client.site.properties
files on your Information Server directory structure. There should be
only one iis.client.site.properties file on the server.
6) Rerun the import.

Popular posts from this blog

Shrink you container size up to 95%.

-
BLAFS is a bloat-aware filesystem for container debloating. The design principles of BLAFS are effective, efficient, and easy to use. It detects the files used by the container, and then debloats the container by removing the unused files. The debloated containers are still functional and can run the same workload as the original containers, but with a much smaller size and faster deployment. https://github.com/negativa-ai/BLAFS?tab=readme-ov-file
Read more

alma linux: dnf Module yaml error: Unexpected key in data

-
While applying recent updates to a server running Rocky Linux 8, an error presented itself. Module yaml error: Unexpected key in data: static_context [line 9 col 3] Module yaml error: Unexpected key in data: static_context [line 9 col 3] The solution turned out to be a simple one. Update the libmodulemd first to correct the problem then perform the dnf updates as usual. dnf update libmodulemd For a detailed explanation as to the cause of this problem.
Read more