To resolve this issue, increase the connection timeout values.
Procedure
- Take a snapshot of the Usage Meter appliance in vSphere.
- Log in as root to Usage Meter 4.8 and enable SSH:
service sshd start
- SSH connect to the appliance as usagemeter:
ssh usagemeter@<um-ip-address>
- Take a backup copy of collection.yml.
cp /opt/vmware/cloudusagemetering/platform/conf/schedule-executions/collection.yml /opt/vmware/cloudusagemetering/platform/conf/schedule-executions/collection-backup.yml
- Edit the config file using the vi editor. Press i to switch to interactive mode.
vi /opt/vmware/cloudusagemetering/platform/conf/schedule-executions/collection.yml
- Set the connection timeout to 900000 (15 min):
=> vcReceiveTimeoutMillis="900000"
=> sbpmConnectionTimeoutMillis="900000"
=> sbpmConnectionTimeoutMillis="900000"
- Save the file by pressing ESC and then entering:
:wq!
- Take a backup copy of command.yml.
cp /opt/vmware/cloudusagemetering/platform/conf/schedule-executions/command.yml /opt/vmware/cloudusagemetering/platform/conf/schedule-executions/command-backup.yml
- Edit the config file using the vi editor. Press i to switch to interactive mode.
vi /opt/vmware/cloudusagemetering/platform/conf/schedule-executions/command.yml
- Replace the values of the below fields:
-Dsun.net.client.defaultConnectTimeout=600000
-Dsun.net.client.defaultReadTimeout=900000
- Save the file by pressing ESC and then entering:
:wq!
- Restart the appliance as root.
su -
reboot