使用期间发现，com.alibaba.smart.framework.engine.persister.custom.session.PersisterSession.sessionThreadLocal线程被复用，其上下文信息错乱

[canji1983]

使用期间发现，高并发的时候，节点执行的序列化信息在执行过程中出现错乱了，是否与InheritableThreadLocal<Stack> sessionThreadLocal = new InheritableThreadLocal<Stack>();有关：具体代码是：com.alibaba.smart.framework.engine.persister.custom.session.PersisterSession.sessionThreadLocal

public static void destroySession() {
Stack stack = getOrBuildStack(sessionThreadLocal);
stack.pop();

    // 当线程被复用时，导致stack被多个子线程共享，进而导致push/pop 不被成对调用了，最终导致数据错乱。
    if(stack.isEmpty()){
        sessionThreadLocal.remove();
    }
}

猜测跟这块的逻辑有关系，如果线程复用在sessionThreadLocal.remove(); 之前，stack.pop();之后，则无法清理上下文

[vavi]

有具体异常吗? 或者简单的UT来还原下场景, 看看能不能复现下.

[canji1983]

没有UT复现，但是有一些日志和现场信息协助查问题：

1. 这种情况是 序列化信息直接变成空的了：{"processInstances":{}}，导致流程执行卡住
2. 序列化信息 例如definitionId和nodeId，在流程执行的过程中发生错乱，比如流程实例id是808396928，definitionId应该是INST_808396918，出现错乱后，definitionId变成INST_808396920，其下的nodeId也变成其他流程的节点id了
   {
   "processInstances": {
   "808396928": {
   "activityInstances": [
   {
   "executionInstanceList": [
   {
   "active": false,
   "activityInstanceId": "808396934",
   "completeTime": "2025-08-22 13:00:11.427",
   "instanceId": "808396935",
   "processDefinitionActivityId": "startNode",
   "processDefinitionIdAndVersion": "INST_808396920:1.0.0",
   "processInstanceId": "808396928",
   "startTime": "2025-08-22 13:00:11.427"
   }
   ],
   "instanceId": "808396934",
   "processDefinitionActivityId": "startNode",
   "processDefinitionIdAndVersion": "INST_808396920:1.0.0",
   "processInstanceId": "808396928",
   "startTime": "2025-08-22 13:00:11.427"
   },
   {
   "executionInstanceList": [
   {
   "active": false,
   "activityInstanceId": "808396936",
   "completeTime": "2025-08-22 13:00:11.74",
   "instanceId": "808396937",
   "processDefinitionActivityId": "1d9201c0-a4a8-4644-b064-666d96da1815",
   "processDefinitionIdAndVersion": "INST_808396920:1.0.0",
   "processInstanceId": "808396928",
   "startTime": "2025-08-22 13:00:11.427"
   }
   ],
   "instanceId": "808396936",
   "processDefinitionActivityId": "1d9201c0-a4a8-4644-b064-666d96da1815",
   "processDefinitionIdAndVersion": "INST_808396920:1.0.0",
   "processInstanceId": "808396928",
   "startTime": "2025-08-22 13:00:11.427"
   },
   {
   "executionInstanceList": [
   {
   "active": true,
   "activityInstanceId": "808396946",
   "instanceId": "808396947",
   "processDefinitionActivityId": "03819f27-4ddc-44a7-a9d4-f080b81757e9",
   "processDefinitionIdAndVersion": "INST_808396920:1.0.0",
   "processInstanceId": "808396928",
   "startTime": "2025-08-22 13:00:11.74"
   }
   ],
   "instanceId": "808396946",
   "processDefinitionActivityId": "03819f27-4ddc-44a7-a9d4-f080b81757e9",
   "processDefinitionIdAndVersion": "INST_808396920:1.0.0",
   "processInstanceId": "808396928",
   "startTime": "2025-08-22 13:00:11.74"
   }
   ],
   "instanceId": "808396928",
   "processDefinitionId": "INST_808396920",
   "processDefinitionIdAndVersion": "INST_808396920:1.0.0",
   "processDefinitionVersion": "1.0.0",
   "startTime": "2025-08-22 13:00:11.426",
   "status": "running",
   "suspend": false
   }
   }
   }

追查日志发现：序列化信息并不是最开始就是错误的，而是中途发生错乱的，由于例子对应的日志没有存档，无法给出具体的变化，但是能看出来，获取序列化信息的线程名字相同，有复用的情况