Troubleshooting
Problem
"Unexpected data length read from Resource Tracker Socket"
Resolving The Problem
Check to see if port 13450 may be used by any other program (especially if problem began after installing other products onto the same system).
If you suspect that you do have port conflict with another application, and that application cannot change its ports, then you can change the port used by ResMonApp by uncommenting and updating 2 lines in file /opt/IBM/InformationServer/Server/DSODB/DSODBConfig.cfg:
# ResourcePortNum=13450
# ResourceRemotePortNum=13450
After this change, you will need to stop and restart the DSAppWatcher services using the correct userid (usually dsadm). For example:
/opt/IBM/InformationServer/Server/DSODB/bin/DSAppWatcher.sh -stop
/opt/IBM/InformationServer/Server/DSODB/bin/DSAppWatcher.sh -start
Another possible cause of this error occurs when security scanning software tests active ports on a server. If the scanning software sends any data to this port it can trigger the error. In that situation, you may wish to exclude that port from scans.
For sites using Information server 11.5.0.2 or 11.7, you also have the option of enabling a new option to tell ResMonApp to retry using the port rather than terminate. This change was added via APAR JR56142. To enable this fix, you need to insert into file DSODB/DSODBTuning.cfg the line:
RMARetryResTrackPort=1
After this change, you will need to stop and restart the DSAppWatcher services using the correct userid (usually dsadm). For example:
/opt/IBM/InformationServer/Server/DSODB/bin/DSAppWatcher.sh -stop
/opt/IBM/InformationServer/Server/DSODB/bin/DSAppWatcher.sh -start
Document Location
Worldwide
Was this topic helpful?
Document Information
Modified date:
15 July 2021
UID
ibm16472933