This issue occurs when large number of network ranges takes too long to return query which results in timeout.
Resolution
This is a known issue affecting vRealize Automation 7.x
Currently, there is no resolution.
To work around this issue, use one of these options:
Provide search criteria to avoid the timeout and obtain the network range information.
For example:
You can add a custom attribute named VLAN to each network with a corresponding value, such as 4. You can then filter on the VLAN=4 string in the network ranges option on the vRealize Automation network profile page.
Depending on your IPAM provider, add a property named VLAN to each network in the IPAM provider application and assign a value to that property, such as 4. You could then filter on the property and value, for example VLAN=4, in the Select Network Range text box on the vRealize Automation network profile page.
Note: The example is Infoblox specific, VLAN=4 works for Infoblox, but might not work for other IPAM providers.
Increase the timeout setting:
Open the /etc/vcac/webapps/o11n-gateway-service/WEB-INF/classes/META-INF/spring/root/o11n-gateway-service-context.xml file of the vRealize Automation appliance node.
Search for the vco.socket.timeout.millis timeout key: