App Connect

 View Only
Expand all | Collapse all

intemittent Database Connection Timeout from message flow

  • 1.  intemittent Database Connection Timeout from message flow

    Posted Fri June 28, 2024 09:08 AM

    Have an APP connect broker application which has within below high level details: 

    • Broker Node -> 1 Execution Group
    • DB connection is setup at Broker level via ODBC DSN setup
    • ~9 message flows
      • each of the message flow interacts with database - runs queries
      • 3 messages flows are continuously being triggered in 1 minute frequency , this could endup with other message flows also getting triggered 

    Issue: 

    • intermittent DB connection issue timeout  is occurring with below error for 1 /2 message flows which doesn't run continuously but gets triggered when some conditions are met, error: 
      • [IBM][ODBC Oracle Wire Protocol driver][Oracle]Network Operation Timed Out.

    Analysis done so far: 

    • no issue with the database connectivity - nothing actually gets logged in database when this issue occurred , its like the connection never reached database and timeout at app itself 
    • Since DB config is at Broker Node level, all message flows are connecting to same database and tables -, doesn't seem to be issue with the table or the data,etc
    • didn't find any config at Broker/Execution group level that limits number of connection 

    Could you please help what could be the possible cause for this. Anything I 've misssed to check so far. Any suggestions will be highly appriciated.



    ------------------------------
    bipin shakya
    ------------------------------


  • 2.  RE: intemittent Database Connection Timeout from message flow

    Posted Mon July 15, 2024 04:59 AM

    Hi Bipin,

    Issues like these need to be dug deep as to what interaction is being done when the message flows are the interacting with Database, If the same record is getting updated by multiple message flows, then it would cause the other process to wait for it's turn, and thus causing it to time out.

    Try looking at what's being done in the message flow from db perspective and dry run any scenario that might cause it to get in a locking situation.

    Regards,

    Muhammad Uzair



    ------------------------------
    Muhammad Uzair Arif
    ------------------------------