yipixiaofeiyang commented on issue #14254:
URL: https://github.com/apache/dubbo/issues/14254#issuecomment-2136630274

   > I don't understand what this is, kill the process will call destroy logic, 
set a set of identifiers, and then when the business method is called again, 
the exception will appear
   > 
   > 
![image](https://private-user-images.githubusercontent.com/56506697/334669262-9ac03c98-0cf7-4728-a721-349a2d01fe66.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTY5NjQxMDQsIm5iZiI6MTcxNjk2MzgwNCwicGF0aCI6Ii81NjUwNjY5Ny8zMzQ2NjkyNjItOWFjMDNjOTgtMGNmNy00NzI4LWE3MjEtMzQ5YTJkMDFmZTY2LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA1MjklMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNTI5VDA2MjMyNFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTg5Mzc0ZTdiYmZjMDY5OTk1ZWYwZTI3M2JkZmI5MDdiZWUzZjc5MWMxYjMyZjZmNjhmYzhkZDFmOTJmMDQyM2QmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.9UhO_NAJ3xh_jKR9QPBj3rKAqU7Xsmkdg-Bx2r09rCo)
   > 
   > I didn't think of any practical significance in this scenario?
   
   Kill the running consumer service first, then restart the service. 
Continuously accessing the Spring interface during this process can cause this 
problem. Some people online claim that it was caused by the shutdown of the 
Dubbo service before the Spring service. After comparing the changes in 3.1.5 
and 3.1.6, we did not find the reason. Could you please help analyze the 
question


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to