Error : Commit failed, rollback previously requested by nested transaction
We are unable to sync components to linked issues while moving the transition getting below error.
org.ofbiz.core.entity.GenericTransactionException: Commit failed, rollback previously requested by nested transaction.
We are using "Write field on linked issues or subtasks" post function to sync the components on linked issues and then change the status. But we are getting above error.
you can find the attached screenshot for more information.
Please help to fix the issue ASAP.
Thanks, Raj Kumar
Comments (22)
-
repo owner -
reporter Thank you for your response. Please find the attached.
Regards, Raj Kumar
-
reporter Thank you. Shared the details on given ID
-
repo owner Can you, please, confirm the version of JIRA Workflow Toolbox you are using?
-
reporter JIRA Workflow Toolbox version is 2.2.28
-
repo owner And the version of JIRA, please?
-
reporter JIRA Version 7.1.9
-
repo owner Hi Raj,
I can see in your log file that you have updated from JIRA Workflow Toolbox 2.2.13 to 2.2.28 after doing all the testing. So all the error messages registered are generated by version 2.2.13.
Can you please, try to reproduce the errors using version 2.2.28 and send me the log file?
On the other hand, can you, please, tell me whether you have any listeners configured in your JIRA instance? In affirmative case, can you please share the configuration of the listener with me?
Thanks.
-
reporter Hi Fidel,
Any update on this issue ? Thanks
-
repo owner Raj,
Sorry, I think you didn't notice (read) my previous post. I'm still waiting for your answers to it. I need the following information:
- Please, try to reproduce the errors using version 2.2.28 and send me the log file.
- Please, tell me whether you have any listeners configured in your JIRA instance? In affirmative case, please share the configuration of the listener with me?
-
reporter I sent the logs on support@workflowarts.com.
-
repo owner Raj,
In the new log file I don't see any errors after updating to version 2.2.28, but before (i.e., with version 2.2.13). Have you tried to reproduce the error after updating to version 2.2.28?
Can you please try disabling the listener and see whether it solves the problem?
-
reporter Hi Fedal,
We have disabled the listner and tried. But getting same error.
We are using same configuration in other transition as well. But we are not using component fields there. But there it's working fine. We are getting the issue with component field only.
Thanks
-
repo owner Hi Raj,
As I told you, in the last log file you sent to me there isn't any error message after installing version 2.2.28.
Can you please reproduce the error with version 2.2.28 and send me the log file?
I need to see the error messages in the log file with version 2.2.28.
Sorry, for so many requirements from my part, but I need that information.
Thank you for your patience.
-
reporter Recently generated error. Sent the complete log file in separate mail. Thanks
2017-01-11 15:46:29,971 Caesium-1-3 ERROR anonymous RSYS JIRA Handler [c.a.jira.mail.MailThreadManagerImpl] Unable to parse incoming In-Reply-To header JIRA.27636.1479139307069@jira 2017-01-11 15:46:31,325 http-nio-8080-exec-13 WARN bshankar 946x9817604x1 emac3x 172.24.42.139,172.24.100.73 /browse/ATTFLEX-9 [c.a.j.i.search.util.SearchPropertiesManager] Invalid filter ID in user preferences: 2017-01-11 15:46:52,204 http-nio-8080-exec-12 ERROR rakumar 946x9817723x1 pdsuxu 172.24.20.71,172.24.100.73 /secure/CommentAssignIssue.jspa [c.a.jira.transaction.TransactionSupportImpl] Unable to commit transaction : Commit failed, rollback previously requested by nested transaction. org.ofbiz.core.entity.GenericTransactionException: Commit failed, rollback previously requested by nested transaction. at org.ofbiz.core.entity.TransactionUtil.commitLocalTransaction(TransactionUtil.java:342) at com.atlassian.core.ofbiz.util.CoreTransactionUtil.commit(CoreTransactionUtil.java:41) at com.atlassian.jira.transaction.TransactionSupportImpl$TransactionImpl.commit(TransactionSupportImpl.java:76) at com.atlassian.jira.workflow.OSWorkflowManager.doWorkflowActionInsideTxn(OSWorkflowManager.java:833) at com.atlassian.jira.workflow.OSWorkflowManager.doWorkflowAction(OSWorkflowManager.java:786) at com.atlassian.jira.bc.issue.DefaultIssueService.transition(DefaultIssueService.java:484) at com.atlassian.jira.web.action.issue.CommentAssignIssue.doExecute(CommentAssignIssue.java:162) ... 1 filtered at com.atlassian.jira.action.JiraActionSupport.execute(JiraActionSupport.java:63) ... 7 filtered at javax.servlet.http.HttpServlet.service(HttpServlet.java:729) ... 50 filtered at com.atlassian.greenhopper.jira.filters.ClassicBoardRouter.doFilter(ClassicBoardRouter.java:59) ... 62 filtered at com.atlassian.jira.security.JiraSecurityFilter.doFilter(JiraSecurityFilter.java:70) ... 89 filtered at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) at java.lang.Thread.run(Thread.java:745) 2017-01-11 15:46:52,208 http-nio-8080-exec-12 ERROR rakumar 946x9817723x1 pdsuxu 172.24.20.71,172.24.100.73 /secure/CommentAssignIssue.jspa [c.a.jira.workflow.OSWorkflowManager] Caught exception while attempting to perform action 71 from workflow 38501 on issue 'TGTEST-18' com.atlassian.jira.transaction.TransactionRuntimeException: org.ofbiz.core.entity.GenericTransactionException: Commit failed, rollback previously requested by nested transaction. at com.atlassian.jira.transaction.TransactionSupportImpl$TransactionImpl.commit(TransactionSupportImpl.java:80) at com.atlassian.jira.workflow.OSWorkflowManager.doWorkflowActionInsideTxn(OSWorkflowManager.java:833) at com.atlassian.jira.workflow.OSWorkflowManager.doWorkflowAction(OSWorkflowManager.java:786) at com.atlassian.jira.bc.issue.DefaultIssueService.transition(DefaultIssueService.java:484) at com.atlassian.jira.web.action.issue.CommentAssignIssue.doExecute(CommentAssignIssue.java:162) ... 1 filtered at com.atlassian.jira.action.JiraActionSupport.execute(JiraActionSupport.java:63) ... 7 filtered at javax.servlet.http.HttpServlet.service(HttpServlet.java:729) ... 50 filtered at com.atlassian.greenhopper.jira.filters.ClassicBoardRouter.doFilter(ClassicBoardRouter.java:59) ... 62 filtered at com.atlassian.jira.security.JiraSecurityFilter.doFilter(JiraSecurityFilter.java:70) ... 89 filtered at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) at java.lang.Thread.run(Thread.java:745) Caused by: org.ofbiz.core.entity.GenericTransactionException: Commit failed, rollback previously requested by nested transaction. at org.ofbiz.core.entity.TransactionUtil.commitLocalTransaction(TransactionUtil.java:342) at com.atlassian.core.ofbiz.util.CoreTransactionUtil.commit(CoreTransactionUtil.java:41) at com.atlassian.jira.transaction.TransactionSupportImpl$TransactionImpl.commit(TransactionSupportImpl.java:76) ... 221 more 2017-01-11 15:47:05,419 http-nio-8080-exec-21 WARN mkedia 947x9817796x2 zjhsu4 172.24.41.113,172.24.100.73 /secure/AjaxIssueAction!default.jspa [c.a.j.i.search.util.SearchPropertiesManager] Invalid filter ID in user preferences: 2017-01-11 15:47:17,248 http-nio-8080-exec-37 WARN bshankar 947x9817810x1 emac3x 172.24.42.139,172.24.100.73 /secure/AjaxIssueAction!default.jspa [c.a.j.i.search.util.SearchPropertiesManager] Invalid filter ID in user preferences: 2017-01-11 15:47:18,153 http-nio-8080-exec-25 WARN mkedia 947x9817818x1 zjhsu4 172.24.41.113,172.24.100.73 /browse/CAMBGE-130 [c.a.j.i.search.util.SearchPropertiesManager] Invalid filter ID in user preferences:
-
repo owner Raj,
That error message doesn't seem to be caused by JIRA Workflow Toolbox. I can see other error messages generated by JIRA Workflow Toolbox, but seem to have disappeared after update to 2.2.28.
I have tried to reproduce your problem using version 2.2.28 and JIRA 7.1.9, and in my case I'm using successfully "Write field on linked issues or subtasks" post-function for copying Components into linked issues.
I would like to see the problem in direct. Can we have a video-conference with screen-share through Skype? My user is fidel100r? I will be available for the next 2 hours, until 13:30 UTC.
-
reporter HI Fidel,
Can you please provide your email ID, So I can send skype email invitation we are using Business for Skype so need email ID to send the meeting information.
-
reporter HI Fidel,
Please let me know once you will be available today. We can discuss on TeamViewer. You can install TeamViewer from below URL.
https://download.teamviewer.com/download/TeamViewer_Setup_en.exe
-
repo owner Hi Raj,
I will be available from now to 13:30 UTC at Skype (my email at Skype is fidel@workflowarts.com) or at TeamViewer.
-
reporter - changed status to resolved
The issue got resolved after doing some changes in validator.
Thank you Fidel for your great support
-
I am having the exact same issue , @Raj Kumar @Fidel , Can you please assist and let me know how did you resolve this back then ?
Thanks,
Ajinkya
-
Hi Team,
We are also facing same issue.
what changes we need to do in validator ?
- Log in to comment
Hi Raj,
I need the following information: