Network Communication Failures

Follow

Jeffery Brown

• September 20, 2018 18:47

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)? "

1

• 

  Parker Phinney

  • October 15, 2018 19:55

  We are experiencing similar network connection break issues. It would be helpful to get more insight into why connection breaks occur. They are limited in the number of times they happen but frustrating because you cannot take action to prevent. 

  0

  Comment actions Permalink
• 

  JL Macatula

  • October 15, 2018 20:07

  Hmmmm interesting....  what type of errors are you getting?  And between what systems are the connections getting broken? We do experience network "hiccups" every once in a while and cannot find the root cause of it. I hate to close out an issue unsolved :(  

  0

  Comment actions Permalink
• 

  Parker Phinney

  • October 15, 2018 20:11

  Infogix Cloud and our network. I think  we know that there is a timeout setting when Assure runs too long. There should be a "Heartbeat" function coming (I believe). But there are other outages that we have not explained. Doesn't happen often, last time was in August.

   

  0

  Comment actions Permalink
• 

  JL Macatula

  • October 15, 2018 20:29

  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=true

  A 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.

   

   

   

  0

  Comment actions Permalink
• 

  Jeffery Brown

  • October 16, 2018 14:54

  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.

  0

  Comment actions Permalink

Please sign in to leave a comment.