we have a Jira 7.13 Instance (see *1)) that makes extensive use of apps, scripting and automations.
It rarely has more than 5 users working on it concurrently but the actions they perform are quite load-intensive.
When the load on the system rises we sometimes get Exceptions like this:
2021-04-20 16:35:43,129 http-nio-127.0.0.1-8080-exec-193 ERROR s.xxxxx 995x540616x1 1cy303 22.214.171.124,127.0.0.1 /secure/CommentAssignIssue.jspa [c.o.s.jira.workflow.AbstractScriptWorkflowFunction] Script function failed on issue: WB-48741, actionId: 31, file: null
com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericDataSourceException: SQL Exception while executing the following:SELECT pkey, issuenum, PROJECT, REPORTER, ASSIGNEE, CREATOR, issuetype, SUMMARY, DESCRIPTION, ENVIRONMENT, PRIORITY, RESOLUTION, issuestatus, CREATED, UPDATED, DUEDATE, RESOLUTIONDATE, VOTES, WATCHES, TIMEORIGINALESTIMATE, TIMEESTIMATE, TIMESPENT, WORKFLOW_ID, SECURITY, FIXFOR, COMPONENT FROM public.jiraissue WHERE ID=? (ERROR: current transaction is aborted, commands ignored until end of transaction block)
Full Exception: here
Starting with this exception every SQL call the system makes within this web request fails.
I want to understand better what is happening there.
My Interpreation so far:
ERROR: current transaction is aborted, commands ignored until end of transaction block)
The current database transaction was aborted in Postgres. Therefore Postgres doesnt execute any selects or other sql statements any more until a new transaction is started.
Who requested to abort the transaction? There is nothing suspicious in the atlassian-jira.log above this exception.
Did Postgres abort the transaction? Or did Jira order Postgres to do so?
Whoever did it, why does it do that?
It seems to be related to this error message that appears in the postgresql-9.6-main.log
This message always preceeds the occurrences of the other "Transaction aborted" Exceptions
2021-04-19 07:00:37.776 CEST  jira@jiradb ERROR: canceling statement due to user request
2021-04-19 07:00:37.776 CEST  jira@jiradb CONTEXT: while updating tuple (504,154) in relation "AO_60DB71_LEXORANK"
2021-04-19 07:00:37.776 CEST  jira@jiradb STATEMENT: UPDATE public."AO_60DB71_LEXORANK" SET "LOCK_HASH" = $1, "LOCK_TIME" = $2 WHERE "ID" IN ($3, $4) AND ("LOCK_HASH" IS NULL OR "LOCK_TIME" < $5)
*1) im am aware the instance is beyond it's EOL, an upgrade is planned but we cannot update the instance on short notice because of other requirements with higher priority in this project
To resolve this issue we would be willing to pay some of your work.
Mention me to contact me about that.
Jira is a great tool to use across different departments. Forget that paperwork – switch to Jira and get that tasks done smoothly. Marketing Jira allows for a complete digital transformation of you...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events