For the timeout part, it's the hardest part of ServiceComb Pack. Current we just deal it in a simple way： Once the ServiceInvoker (Hotel) found out there is a timeout event, it just send AbortEvent to the Alpha and end the whole transaction.
For the TxEnded after the TxAbortEvent issue, we can address it by letting Omega throw the exception when it received the response from Alpha (Alpha should know the transaction is aborted at that time) In this way, we could leverage the @Tranactional feature that Spring provides to revert the local transaction without sending out the compensation command. Any thought about that? Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Thu, Mar 21, 2019 at 11:47 AM [email protected] <[email protected]> wrote: > > The following link is a sequence diagram, step 4 cannot be compensated. Will > this happen? > > https://github.com/coolbeevip/servicecomb-pack-notes/blob/master/ServiceComb%20Alpha%20EventScanner/assets/sequence-booking-request-hotel-timeout.png?raw=true > > coolbeevip > ———————————————————————— > BOCO > > >
