SourceOrderAction - Getting Transaction rolled back because it has been marked as rollback-only

[nagoorbashashaik_ta]

Hi,

We are getting Transaction rolled back because it has been marked as rollback-only exception in SourceOrderAction in SAP Commerce Cloud and consignment process is not getting created. This is occurring ONLY in SAP Commerce Cloud. It is working fine in local machine.

We are using SAP Commerce v 2005 and done the setup with cx recipe and yacceleratorordermanagement. and there is no customization done in order management.

Do you know why do we get this error and how to resolve it?

[nagoorbashashaik_ta]

Here are the SourceOrderAction logs:

INFO  [TaskExecutor-master-1633-ProcessTask [8797536519094]] 12:06:25.834   Process: order-process000180061598366135237 in step SourceOrderAction
INFO  [TaskExecutor-master-1633-ProcessTask [8797536519094]] 12:06:25.842   Sourcing from Location: 'pw_warehouse_n'
INFO  [TaskExecutor-master-1633-ProcessTask [8797536519094]] 12:06:25.843   	Product [echo_dot_3]: 'Echo Dot (3rd Gen)'	Quantity: '2'
INFO  [TaskExecutor-master-1633-ProcessTask [8797536519094]] 12:06:26.252   Start Consignment sub-process: 'cons00018006_0_ordermanagement'
INFO  [TaskExecutor-master-1633-ProcessTask [8797536519094]] 12:06:26.256   Order was successfully sourced 
ERROR [TaskExecutor-master-1633-ProcessTask [8797536519094]] 12:06:26.297   Transaction rolled back because it has been marked as rollback-only

Here is Stack Trace :

stacktrace.txt

[sohampingle]

Hello nagoorbashashaik_ta,

I am also facing similar issue, could you find the root cause?

[amol_panode]

Hi nagoorbashashaik I am also getting exact same issue with SAP Commerce Cloud version 2005 on my local and SAP cloud environment. Did you find any solution for it?

[bhavirisetty]

we also have the same issue, found any solution? Thank you.

[nagoorbashashaik_ta]

Looks like it is related to DB inactive sessions. As it has happened in lower environment and DB capacity is very less, we have removed the unnecessary data and stopped unnecessary cronjobs which results in less DB usage.

This resolved the issue.

[lars_mueller3]

Hi bhavirisetty36,

how have you solved it?

Thanks,

Lars

[former_member711174]

hi bhavirisetty Did you get any answer on this. If yes then please guide.

[srini_y · Accepted solution]

Root cause:
In SourceOrderAction, the consignments get created by the allocation service. After their creation, the consigment workflow also gets started by DefaultWarehousingConsignmentWorkflowService.startConsignmentWorkflow() method. Here, the employee with lowest load belonging to warehouse's POSs gets fetched from DB and assigned to all the WorkflowActions. All the workflow agents of a particular site (say: powertools) are defined in ordermanagementaddon/import/stores/powertools/points-of-service.impex as shown below:

INSERT_UPDATE StoreEmployeeGroup;UID[unique=true];locname[lang=en];store(name)
;pw_warehouse_s_storeemployees;pw_warehouse_s Store Employee Group;pw_warehouse_s
;pw_warehouse_e_storeemployees;pw_warehouse_e Store Employee Group;pw_warehouse_e
;pw_warehouse_w_storeemployees;pw_warehouse_w Store Employee Group;pw_warehouse_w
;pw_warehouse_n_storeemployees;pw_warehouse_n Store Employee Group;pw_warehouse_n

INSERT_UPDATE Employee;uid[unique=true];name;groups(uid)
;WarehouseSAgent;WarehouseSAgent Warehouse Agent ;warehouseagentgroup,pw_warehouse_s_storeemployees
;WarehouseEAgent;WarehouseEAgent Warehouse Agent ;warehouseagentgroup,pw_warehouse_e_storeemployees
;WarehouseWAgent;WarehouseWAgent Warehouse Agent ;warehouseagentgroup,pw_warehouse_w_storeemployees
;WarehouseNAgent;WarehouseNAgent Warehouse Agent ;warehouseagentgroup,pw_warehouse_n_storeemployee

The passwords for the above agents aren't defined in the impex and upon setting up 2005 CX recipe in our local environments, all the agents will by default be disabled (loginDisabled=true). As these agents are disabled, the below piece of code in DefaultWarehousingConsignmentWorkflowService.startConsignmentWorkflow() throws a ModelSavingException while trying to save WorkflowAction (AbstractWorkflowAction.setPrincipalAssigned() method) as the principalAssigned's loginDisabled=true.

workflow.getActions().forEach(action -> {
					action.setPrincipalAssigned((PrincipalModel) finalSelectedUser);
					this.getModelService().save(action);
				});

The masked exception is JaloSystemException with message Assigned user WarehouseNAgent can not access the hMC as agents are disabled. The log statement "No PrincipalAssigned available for this order. A consignment will still be created." is misleading as we tend to think that Consignment will still be created. However, we end up getting a transaction rollback.

Fix: Set default passwords & enable all the warehouse agents!

[former_member752398 · Accepted solution]

Excellent! Thank you srini_y, you saved my time 🙂