Network Communication Failures
Customer submitted inquiry and discussion topic:
"Coding for network communication failures – most of our issues today can be tracked down to code that doesn’t handle network communication failures. How are other companies handling this internally since it is not being handled by the product (code)? "
-
Ahhhhh.. We haven't done an Infogix cloud to our network type of connection. What we experienced before was between our Mainframe system going to Infogix Assure. We had to adjust this field below in the Assure Server side to prevent it from getting Timeout errors. I would think there is a similar field in the Cloud Assure properties file that handles this between Cloud and your system.
# On/off flag for Keep alive heart beat for streaming client
STREAMING_CLIENT_KEEP_ALIVE=trueA common network error we also get is if we try to connect from Infogix Assure to a database source (internally). They don't come in as often anymore. And normally, if we restart the job, it goes in the second time around. And based on the errors and forums I've visited, these were mostly caused by the driver versions we are using or the Database version of the receiving system.
-
The heartbeat function that Parker is referring too is coming soon and will allow the Assure client to be able to invoke control point processing in the server asynchronously, without retaining a long-running socket connection while the server runs the control point, but will still wait for the control point to finish (including processing of subsequent runcp actions). It's still in development and we should have more information soon.
Please sign in to leave a comment.
Comments
5 comments