← Homepage Orderbox Status Page

Intermittent issue with Orderbox

Opened on June 29th, 2020 10:25 pm GMT, last updated June 30th, 2020 7:13 am GMT

Resolved

Root Cause Analysis:


We noticed that Archived Database connections being assigned to threads initiated via our upgraded Version 2 API code were not being reset after usage. As a result, the same thread was being reused and all subsequent calls were being routed to the Archived Database instead of the Live Database.


The Development Team has added a fix for the same and the issue now stands resolved.


Action Items:


A few long term changes like code optimizations, thread ID logging and exception handling for Version 2 API calls have also been drawn out to ensure that this does not repeat in the future.

Posted June 30th, 2020 7:13 am GMT

Monitoring

We have identified that the Archived DB instance was not being reset after requests were made to the Archived DB for data and hence, connections were failing as the new requests were being routed to the Archived DB instead of the Live DB.


The development team has applied a fix to reset the archived DB instance each time a connect is made to the archived DB


We are monitoring services and will update this thread with more information once a detailed Root Cause Analysis is available to us.

Posted June 30th, 2020 6:12 am GMT

Investigating

We have identified that the issue affects two of our servers and hence, it is observed that the issue is intermittent.


Our development and System Admin teams are reviewing the logs to identify and apply a fix.


If you encounter an error when placing the action, we would request you to re-attempt it a few times so the action processes.


We will update this thread once we have more information from our development team.

Posted June 30th, 2020 3:38 am GMT

Investigating

We are currently facing issues with OrderBox causing intermittent issues while registering a domain, modifying the name servers & making API calls.


Error: could not extract ResultSet; SQL [n/a]; nested exception is org.hibernate.exception.SQLGrammarException: could not extract ResultSet


Our System Administration Team is already working on this issue and are trying to fix this as soon as possible.


We sincerely regret the inconvenience caused. Please watch this thread for further updates.

Posted June 29th, 2020 10:25 pm GMT

Affected Services

  • OrderBox