Confluence Gadget using OAuth mode always calls to generate new access token and store it into database because of the OAuth access token has been expired

The problem happened because JIRA when communicates with Confluence for rendering the gadget using OAuth, JIRA always thinks the stored OAuth access token has been expired so it always tries to contact Confluence for a new access token. However in Confluence whenever a new access token request comes it will creates a new token and stores it into database. It causes very heavy database access to insert the new token and delete the old one. It also cause the problem that we have so many stored tokens in database. Because we have limited number of connections stored in the connection pool so when the pool saturated (heavy db operations happen for tokens deleting and storing) the blocking also go up to Tomcat threads.