Openbravo Issue Tracking System - POS2
View Issue Details
0057611POS2POSpublic2025-01-10 12:342025-03-05 13:29
fermin_ostivar 
meriem_azaf 
normalminoralways
closedfixed 
5
 
 
approved
Gold
No
0057611: Misfired Process Request not saved if channel direct
If a Process Request with channel Direct is misfired, it is not saved in Process Monitor due to an error in the insert query
Set quartz properties to force the scenario:
org.quartz.threadPool.threadCount = 1
org.quartz.jobStore.misfireThreshold = 1


Add a sleep in the VariantChDescUpdateProcess doExecute() to force to take time

Open Product Characteristic tab in backoffice
Modify the name of any product characteristic value two times

Log example:
2025-01-10 12:20:24,890 [DefaultQuartzScheduler_QuartzSchedulerThread] ERROR org.openbravo.scheduling.ProcessRunData - SQL error in query: INSERT INTO AD_Process_Run (AD_Org_ID, AD_Client_ID, Isactive, Created, Createdby, Updated, UpdatedBy, AD_Process_Run_ID, Status, Start_Time, Runtime, Log, AD_Process_Request_ID, Scheduler_Instance) VALUES (?, ?, 'Y', NOW(), ?, NOW(), ?, ?, ?, NOW(), ?, ?, ?, ?) :org.postgresql.util.PSQLException: ERROR: null value in column "ad_process_request_id" violates not-null constraint
  Detail: Failing row contains (D44FDE1FF4114400B0E5D335C051A6A6, 39363B0921BB4293B48383844325E84C, 0, Y, 2025-01-10 12:20:24.884879, 100, 2025-01-10 12:20:24.884879, 100, MIS, 2025-01-10 12:20:24.884879, null, null, null, null, null, null, null, null, null).
To save the misfired process in the Process Monitor tab
No tags attached.
Issue History
2025-01-10 12:34fermin_ostivarNew Issue
2025-01-10 12:34fermin_ostivarAssigned To => Retail
2025-01-10 12:34fermin_ostivarOBNetwork customer => Gold
2025-01-10 12:34fermin_ostivarTriggers an Emergency Pack => No
2025-01-10 12:41guillermogilAssigned ToRetail => Triage Platform Base
2025-01-21 09:48AugustoMauchSteps to Reproduce Updatedbug_revision_view_page.php?rev_id=29085#r29085
2025-01-21 18:34AugustoMauchStatusnew => acknowledged
2025-02-04 10:40javietxeRelationship addedduplicate of 0057008
2025-02-04 10:41javietxeRelationship deleted0057008
2025-02-21 10:09AugustoMauchAssigned ToTriage Platform Base => meriem_azaf
2025-02-24 09:43AugustoMauchStatusacknowledged => scheduled
2025-03-04 13:05hgbotMerge Request Status => open
2025-03-04 13:05hgbotNote Added: 0176425
2025-03-05 10:12hgbotMerge Request Statusopen => approved
2025-03-05 13:29hgbotNote Added: 0176476
2025-03-05 13:29hgbotResolutionopen => fixed
2025-03-05 13:29hgbotStatusscheduled => closed
2025-03-05 13:29hgbotFixed in Version => PR25Q2
2025-03-05 13:29hgbotNote Added: 0176477

Notes
(0176425)
hgbot   
2025-03-04 13:05   
Merge Request created: https://gitlab.com/orisha-group/bu-commerce/openbravo/product/openbravo/-/merge_requests/1567 [^]
(0176476)
hgbot   
2025-03-05 13:29   
Merge request merged: https://gitlab.com/orisha-group/bu-commerce/openbravo/product/openbravo/-/merge_requests/1567 [^]
(0176477)
hgbot   
2025-03-05 13:29   
Directly closing issue as related merge request is already approved.

Repository: https://gitlab.com/orisha-group/bu-commerce/openbravo/product/openbravo [^]
Changeset: 574db30a6b39e56fd5533a28e1e4f0ac4a927705
Author: Augusto Mauch <amauch@orisha.com>
Date: 05-03-2025 09:38:44
URL: https://gitlab.com/orisha-group/bu-commerce/openbravo/product/openbravo/-/commit/574db30a6b39e56fd5533a28e1e4f0ac4a927705 [^]

Fixes ISSUE-57611: Trigger misfire is now properly inserted

The problem was that the process request id was being set to the process bundle, because the ProcessBundle
constructor use did not set it (it is not available yet, the process request has not yet been created).

It has been fixed by setting the process request id to the bundle in OBScheduler.schedule, when the process
request is created.

---
M src/org/openbravo/scheduling/OBScheduler.java
M src/org/openbravo/scheduling/ProcessBundle.java
---