[SCB-2004] When the business service startup is not completed, receiving a compensation request will cause gRPC and alpha to reconnect

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: pack-0.6.0
• Fix Version/s: pack-0.6.0
• Component/s: Saga
• Assignee: Lei Zhang
• Reporter: Lei Zhang
• Created: 16/Jun/20 13:49
• Updated: 23/Jun/23 19:29
• Resolved: 03/Mar/21 15:14

Description

If the Alpha's compensation call is received during the business service startup process, compensation failure will occasionally occur

 
Because at startup, it will be connected to Alpha first, and then all compensation methods will be scanned and put to the class CallbackContext, If business service receives a compensation request before CallbackContext initialization, you will get NullPointerExceptionBecause at startup, it will be connected to Alpha first, and then all compensation methods will be scanned and put to the class CallbackContext, If business service receives a compensation request before CallbackContext initialization, you will get NullPointerException

 

  public void apply(String globalTxId, String localTxId, String parentTxId, String callbackMethod, Object... payloads) {
    CallbackContextInternal contextInternal = contexts.get(callbackMethod); <----- this is empty
    String oldGlobalTxId = omegaContext.globalTxId();
    String oldLocalTxId = omegaContext.localTxId();
    try {
      omegaContext.setGlobalTxId(globalTxId);
      omegaContext.setLocalTxId(localTxId);
      contextInternal.callbackMethod.invoke(contextInternal.target, payloads);
      if (omegaContext.getAlphaMetas().isAkkaEnabled()) {
        sender.send(
            new TxCompensateAckSucceedEvent(omegaContext.globalTxId(), omegaContext.localTxId(),
                parentTxId, callbackMethod));
      }

 

Issue Links

• links to: GitHub Pull Request #667