WARN provisioning [host='provisioning-service-app-7890f646cc-nw9j9' thread='consoleproxy' user='' org='' trace='' parent='' span=''] c.v.consoleproxy.async.EventDispatcher.handleOperation:219 - [CP] The selection key channel=java.nio.channels.SocketChannel[connected local=/10.244.0.131:44148 remote=/12.34.56.78:902], selector=sun.nio.ch.EPollSelectorImpl@258a2ac9, interestOps=1, readyOps=1 has been invoked a critical number of times. Closing.
Ping Results from desktop to Aria Automation appliance:
25 packets transmitted, 25 packets received, 0.0% packet loss
Round-trip time min/avg/max/stddev = 0.371/0.485/0.627/0.058 ms
Ping results from vRealize Automation appliance to remote vSphere:
24 packets transmitted, 24 received, 0% packet loss, time 23005ms
Round trip time min/avg/max/mdev = 228.877/230.275/252.392/4.683 ms
If VMRC freezes when launched through vRA, and if increased logging helps VMRC to remain working, then try out the resolution given in this article.
vcac: [component="cafe:console-proxy" priority="WARN" thread="consoleproxy" tenant] com.vmware.consoleproxy.async.EventDispatcher.handleOperation:209 - [CP] The selection key sun.nio.ch.SelectionKeyImpl@3cd819bb has been invoked a critical number of times. Closing
VMware Aria Automation 8.x
VMware vRealize Automation 7.x
This issue occurs if the CRITICAL_COUNT parameter reaches the limit (default 100) due to which the connection do not catch up the packets transmitted.
Adding the consoleproxy.connection.criticalcount=500 property in the security.properties file for 7.x or in the provisioning-service-app deployment for 8.x resolves the issue.
kubectl -n prelude edit deployment provisioning-service-app
-Dconsoleproxy.connection.criticalcount=500
JAVA_OPTS
list.CRITICAL_COUNT set to
". It shows the current critical count and validates if it picked up the value you set.
The preceding steps do not persist through a restart. To have the changes persist a restart in 8.x the below steps can be performed.
Note that some downtime is expected as the deploy.sh script restarts all pods, not just the provisioning service.