1. Home
  2. Support
Article - CS306534

When running multiple workflows in succession, workflows randomly shutdown with error "[AMQP] conn error write ECONNRESET" in ThingWorx 8.4 Flow-Exchange

Modified: 05-Nov-2019   


Applies To

  • ThingWorx Platform 8.4

Description

  • Sometimes when running multiple flows one after another, errors are received and flow stops executing:

2|flow-exc | initializing db settings
2|flow-exc | Configuring SecurityManager
2|flow-exc | Configured SecurityManager
2|flow-exc | settings set
2|flow-exc | initializing bookshelf on mssql database
2|flow-exc | Knex:warning - Connection Error: ConnectionError: Failed to connect to localhost:1433 - Could not connect (sequence)
2|flow-exc | Configuring SecurityManager
2|flow-exc | Configured SecurityManager
2|flow-exc | Configuration Loaded from C:\ThingWorxOrchestration\modules\exchange/config.json
2|flow-exc | Found Configuration: C:\ThingWorxOrchestration\modules\exchange/deploymentConfig.json
2|flow-exc | initializing db settings
2|flow-exc | Configuring SecurityManager
2|flow-exc | Configured SecurityManager
2|flow-exc | settings set
2|flow-exc | initializing bookshelf on mssql database

C:\ThingWorxOrchestration\.pm2\logs\flow-exchange-error-2.log last 15 lines:
2|flow-exc | {"module":"flow-exchange","timestamp":"2019-04-11T19:03:41.288Z","level":"error","message":"{}"}
2|flow-exc | {"module":"flow-exchange","timestamp":"2019-04-11T19:24:52.030Z","level":"error","message":"{}"}
2|flow-exc | {"module":"flow-exchange","timestamp":"2019-04-11T19:29:52.474Z","level":"error","message":"{}"}
2|flow-exc | {"module":"flow-exchange","timestamp":"2019-04-11T19:51:38.013Z","level":"error","message":"{}"}
2|flow-exc | {"module":"flow-exchange","timestamp":"2019-04-11T20:39:59.719Z","level":"error","message":"{}"}
2|flow-exc | {"module":"flow-exchange","timestamp":"2019-04-11T20:45:00.114Z","level":"error","message":"{}"}
2|flow-exc | <day>, DD MMM YYYY hh:mm:ss GMT tedious deprecated The default value for `options.encrypt` will change from `false` to `true`. Please pass `false` explicitly if you want to retain current behaviour. at node_modules\mssql\lib\tedious.js:230:23
2|flow-exc |

{"module":"flow-exchange","timestamp":"YYYY-MM-DDThh:mm:ss.348Z","level":"error","message":"[AMQP] conn error write ECONNRESET"}

2|flow-exc |

{"module":"flow-exchange","timestamp":"YYYY-MM-DDThh:mm:ss.348Z","level":"error","message":"[AMQP] conn error read ECONNRESET"}

2|flow-exc | <day>, DD MMM YYYY hh:mm:ss GMT tedious deprecated The default value for `options.encrypt` will change from `false` to `true`. Please pass `false` explicitly if you want to retain current behaviour. at node_modules\mssql\lib\tedious.js:230:23
2|flow-exc |

{"module":"flow-exchange","timestamp":"YYYY-MM-DDThh:mm:ss.931Z","level":"error","message":"failed to get uid code USER_AUTH_NOT_FOUND"}

2|flow-exc |

{"module":"flow-exchange","timestamp":"YYYY-MM-DDThh:mm:ss.931Z","level":"error","message":"Unable to get auths or connections for execution: failed to get uid code"}

2|flow-exc |

{"module":"flow-exchange","timestamp":"YYYY-MM-DDThh:mm:ss.931Z","level":"error","message":"Error preparing flow for execution: Unable to get auths or connections for execution"}

2|flow-exc |

{"module":"flow-exchange","timestamp":"YYYY-MM-DDThh:mm:ss.931Z","level":"error","message":"failed to get uid code USER_AUTH_NOT_FOUND"}

2|flow-exc |

{"module":"flow-exchange","timestamp":"YYYY-MM-DDThh:mm:ss.931Z","level":"error","message":"failed to get uid code USER_AUTH_NOT_FOUND"}
This is a printer-friendly version of Article 306534 and may be out of date. For the latest version click CS306534