
|
If you were logged in you would be able to see more operations.
|
|
|
|
Environment:
|
WebLogic Server 7.0 SP4
|
|
| Participants: |
Jeff Turner [Atlassian]
|
| Since last comment: |
4 years, 15 weeks, 4 days ago
|
| Resolution Date: |
12/May/04 12:11 AM
|
| Labels: |
|
When creating an issue, JIRA hangs. The last message in the logs is:
[INFO] StoreFactory - -Initializing WorkflowStore: com.opensymphony.workflow.spi.ofbiz.OfbizWorkflowStore^M
After a log time, the following exception may print in the logs:
org.ofbiz.core.entity.GenericDataSourceException: SQL Exception while executing the following:INSERT INTO OS_HISTORYSTEP (ID,
ENTRY_ID, STEP_ID, ACTION_ID, OWNER, START_DATE, DUE_DATE, FINISH_DATE, STATUS, CALLER) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?)
(ORA-00001: unique constraint (JIRA.PK_OS_HISTORYSTEP) violated^M
)^M
at org.ofbiz.core.entity.jdbc.SQLProcessor.executeUpdate(SQLProcessor.java:341)^M
at org.ofbiz.core.entity.GenericDAO.singleInsert(GenericDAO.java:115)^M
at org.ofbiz.core.entity.GenericDAO.singleStore(GenericDAO.java:242)^M
at org.ofbiz.core.entity.GenericDAO.storeAll(GenericDAO.java:285)^M
at org.ofbiz.core.entity.GenericHelperDAO.storeAll(GenericHelperDAO.java:221)^M
at org.ofbiz.core.entity.GenericDelegator.storeAll(GenericDelegator.java:1472)^M
at org.ofbiz.core.entity.GenericDelegator.storeAll(GenericDelegator.java:1418)^M
at com.opensymphony.workflow.spi.ofbiz.OfbizWorkflowStore.moveToHistory(OfbizWorkflowStore.java:283)^M
at com.opensymphony.workflow.AbstractWorkflow.createNewCurrentStep(AbstractWorkflow.java:1016)^M
at com.opensymphony.workflow.AbstractWorkflow.transitionWorkflow(AbstractWorkflow.java:1327)^M
at com.opensymphony.workflow.AbstractWorkflow.doAction(AbstractWorkflow.java:502)^M
at com.atlassian.jira.workflow.OSWorkflowManager.doWorkflowAction(OSWorkflowManager.java:150)^M
at com.atlassian.jira.web.action.workflow.SimpleWorkflowAction.doExecute(SimpleWorkflowAction.java:23)^M
at webwork.action.ActionSupport.execute(ActionSupport.java:151)^M
|
|
Description
|
When creating an issue, JIRA hangs. The last message in the logs is:
[INFO] StoreFactory - -Initializing WorkflowStore: com.opensymphony.workflow.spi.ofbiz.OfbizWorkflowStore^M
After a log time, the following exception may print in the logs:
org.ofbiz.core.entity.GenericDataSourceException: SQL Exception while executing the following:INSERT INTO OS_HISTORYSTEP (ID,
ENTRY_ID, STEP_ID, ACTION_ID, OWNER, START_DATE, DUE_DATE, FINISH_DATE, STATUS, CALLER) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?)
(ORA-00001: unique constraint (JIRA.PK_OS_HISTORYSTEP) violated^M
)^M
at org.ofbiz.core.entity.jdbc.SQLProcessor.executeUpdate(SQLProcessor.java:341)^M
at org.ofbiz.core.entity.GenericDAO.singleInsert(GenericDAO.java:115)^M
at org.ofbiz.core.entity.GenericDAO.singleStore(GenericDAO.java:242)^M
at org.ofbiz.core.entity.GenericDAO.storeAll(GenericDAO.java:285)^M
at org.ofbiz.core.entity.GenericHelperDAO.storeAll(GenericHelperDAO.java:221)^M
at org.ofbiz.core.entity.GenericDelegator.storeAll(GenericDelegator.java:1472)^M
at org.ofbiz.core.entity.GenericDelegator.storeAll(GenericDelegator.java:1418)^M
at com.opensymphony.workflow.spi.ofbiz.OfbizWorkflowStore.moveToHistory(OfbizWorkflowStore.java:283)^M
at com.opensymphony.workflow.AbstractWorkflow.createNewCurrentStep(AbstractWorkflow.java:1016)^M
at com.opensymphony.workflow.AbstractWorkflow.transitionWorkflow(AbstractWorkflow.java:1327)^M
at com.opensymphony.workflow.AbstractWorkflow.doAction(AbstractWorkflow.java:502)^M
at com.atlassian.jira.workflow.OSWorkflowManager.doWorkflowAction(OSWorkflowManager.java:150)^M
at com.atlassian.jira.web.action.workflow.SimpleWorkflowAction.doExecute(SimpleWorkflowAction.java:23)^M
at webwork.action.ActionSupport.execute(ActionSupport.java:151)^M |
Show » |
|
the OFBiz persistence engine and Weblogic's JTA implementation. Within a transaction, anything that requests a Connection object from the pool should get the same one. For some reason, OSWorkflow's second operation was getting allocated a new Connection not enlisted in the transaction.
This second operation therefore hangs waiting for the first transaction to complete.
As JIRA has no need for transactions anyway, and disables them in Tomcat, Resin and Websphere, the solution was to disable them in Weblogic too.