search

bcgov / entity

ServiceBC Registry Team working on Legal Entities
Apache License 2.0
23 stars 58 forks source link

BCOL-API - Investigate retry mechanism for request failure #20064

Open seeker25 opened 8 months ago

seeker25 commented 8 months ago

Right now we have an issue where we make a request and lose a connection. This causes us to not receive the response, even if it was successful (confirmed by BCOL home team). This can lead to orphaned records inside of BCONLINE, that don't exist in SBC-PAY.

This ticket is a proposal to look into a building a retry mechanism if a connection is lost. It's possible BCOL will throw a duplicate transaction error, in this scenario the invoice can be confirmed as created and not rollback PAY-API.

seeker25 commented 8 months ago

Hey team! Please add your planning poker estimate with Zenhub @Jxio @ochiu @rodrigo-barraza

seeker25 commented 8 months ago

Note: BCOL Test environment doesn't seem to be working currently, contact is Thayne

seeker25 commented 8 months ago

More context:

Hi Chris,
The example provided below is excellent and actually corresponds to an outage of 10 minutes of Wednesday Jan 17 morning.  I actually have an outstanding ticket with HP/DXCAS asking for information on what occurred.  This affected the GARMS application but only for selected offices still the perception was that the application was down.  In fact IMS was not impacted so any transaction that were queued for execution would completed but as in this case the thread had been orphaned due to the timeout as a result of the connectivity issue.

I am wondering if perhaps you could find another example outside this timeframe.

John