The contents of the Service Grid Ingress Connector started up before the connection to the Data Hub was entirely established. Thus, not all objects were correctly connected and the Web Engine request for advising variables was rejected. Now, these contents startup after the connection to the Data Hub reports a valid state and the Web Engine can immediately and correctly reconnect. Additionally, the sending of the runtime information is delayed until the contents finished startup. Thus, the Web Engine gets the notification to reconnect after all listeners are running inside Service Grid Ingress Connector. Plus: the protocol stack could not handle fast incoming unadvise-and-readvise commands that happen inside the Web Engine upon a screen reload. That has been fixed too.
The contents of the Service Grid Ingress Connector started up before the connection to the Data Hub was entirely established. Thus, not all objects were correctly connected and the Web Engine request for advising variables was rejected. Now, these contents startup after the connection to the Data Hub reports a valid state and the Web Engine can immediately and correctly reconnect. Additionally, the sending of the runtime information is delayed until the contents finished startup. Thus, the Web Engine gets the notification to reconnect after all listeners are running inside Service Grid Ingress Connector. Plus: the protocol stack could not handle fast incoming unadvise-and-readvise commands that happen inside the Web Engine upon a screen reload. That has been fixed too.