Transaction-related errors

When running an graph that starts an outer transaction, the graph fails and an error such as the following is reported in the Console Log:

ERROR [ENDECA_TRANSACTION_RUN_GRAPH0_0] - Connection refused: connect Error starting transaction ID transaction. Ensure another transaction isn't already in progress.
ERROR [ENDECA_TRANSACTION_RUN_GRAPH0_0] - Connection refused: connect Error running internal sub graphs
INFO  [ENDECA_TRANSACTION_RUN_GRAPH0_0] - Transaction ID 'transaction' still open, but configured to do nothing

These errors may occur for the following reasons:

• You have attempted to run multiple graphs that start outer transactions (in other words, multiple graphs that include the Transaction RunGraph component) at the same time.
  • This situation can occur if a graph that runs an outer transaction fails and continues running, and you start another graph that runs an outer transaction.

    To determine whether an outer transaction is currently running, issue a listOuterTransaction request through the Transaction Web Service. If the response includes a value for the outer transaction ID, an uncommitted transaction is still running. To terminate the running transaction, commit it.

  • This situation also occurs if you start multiple graphs that initiate outer transactions at the same time. You can only run one outer transaction at a time. Allow a running outer transaction to complete before starting another outer transaction.
• You have attempted to run a graph that is included in an outer transaction at the same time as are running the outer transaction that includes the graph.

  For example, suppose Graph A includes the Transaction RunGraph component and also includes Graph B as one of the graphs to run within the transaction. If Graph A is running, and you start Graph B, Graph B will fail.