Anonymous | Login
Project:
RSS
  
News | My View | View Issues | Roadmap | Summary

View Issue Details[ Jump to Notes ] [ Issue History ] [ Print ]
ID
0053401
TypeCategorySeverityReproducibilityDate SubmittedLast Update
defect[Retail Modules] Web POSmajoralways2023-09-06 13:572023-09-22 06:52
ReportersofidossantView Statuspublic 
Assigned Tosofidossant 
PrioritynormalResolutionno change requiredFixed in Version
StatusclosedFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionRR21Q4SCM revision 
Review Assigned Toguillermogil
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0053401: Error while importing org.openbravo.base.exception.OBException: paymentData attached to payment

DescriptionWhen the json is very big we have the following error while importing
org.openbravo.base.exception.OBException: paymentData attached to payment 04810000450 - 08-30-2023 - GT Final Consumer - 120.00 is not a valid JSON.
at org.openbravo.retail.posterminal.OrderLoader.processPayments(OrderLoader.java:1826)
at org.openbravo.retail.posterminal.OrderLoader.handlePayments(OrderLoader.java:1484)

Explication:
https://www.youtube.com/watch?v=vF9Bkk19wRY&ab_channel=CristianAdrian%7CPracticsBS [^]
Steps To Reproducein the webpos
Make a sale of many products, and many payments.
Make a cancellation of a card payment in the sale.
And make several payments

In this part, the receipt is added, and it generates that the payment part is very large and generates the ewi

 providerinstance
      .processPayment({
        receipt: receipt,
        currency: currency,
        amount: amount,
        refund: refund,
        providerGroup: providerGroup,
        attributes: attributes
      })
TagsNo tags attached.
Attached Files

- Relationships [ Relation Graph ] [ Dependency Graph ]

-  Notes
(0154873)
hgbot (developer)
2023-09-15 00:48

 Merge Request created: https://gitlab.com/openbravo/product/pmods/org.openbravo.retail.asyncpayprovider/-/merge_requests/24 [^]
(0154874)
hgbot (developer)
2023-09-15 00:49

 Merge Request created: https://gitlab.com/openbravo/product/pmods/org.openbravo.retail.ingenicotsiprovider/-/merge_requests/2 [^]
(0154875)
hgbot (developer)
2023-09-15 00:49

 Merge Request created: https://gitlab.com/openbravo/product/pmods/org.openbravo.retail.adyenprovider/-/merge_requests/30 [^]
(0154876)
hgbot (developer)
2023-09-15 00:49

 Merge Request created: https://gitlab.com/openbravo/product/pmods/org.openbravo.retail.posterminal/-/merge_requests/1341 [^]
(0154915)
guillermogil (manager)
2023-09-18 06:10

 We have been trying to reproduce the behavior and we have not been able to.
Can you provide the implementation that it is failing? Maybe we are checking the async provider and lagacy it being used.
Also, why are we getting an Invalid JSON due to size? is it a valid JSON? Can you share it too?
(0154916)
hgbot (developer)
2023-09-18 06:12

 Merge request closed: https://gitlab.com/openbravo/product/pmods/org.openbravo.retail.posterminal/-/merge_requests/1341 [^]
(0154917)
hgbot (developer)
2023-09-18 06:12

 Merge request closed: https://gitlab.com/openbravo/product/pmods/org.openbravo.retail.adyenprovider/-/merge_requests/30 [^]
(0154918)
hgbot (developer)
2023-09-18 06:12

 Merge request closed: https://gitlab.com/openbravo/product/pmods/org.openbravo.retail.ingenicotsiprovider/-/merge_requests/2 [^]
(0154919)
hgbot (developer)
2023-09-18 06:12

 Merge request closed: https://gitlab.com/openbravo/product/pmods/org.openbravo.retail.asyncpayprovider/-/merge_requests/24 [^]
(0154967)
hgbot (developer)
2023-09-19 06:12

 Merge Request created: https://gitlab.com/openbravo/product/pmods/org.openbravo.retail.posterminal/-/merge_requests/1348 [^]
(0155121)
hgbot (developer)
2023-09-22 06:48

 Merge request closed: https://gitlab.com/openbravo/product/pmods/org.openbravo.retail.posterminal/-/merge_requests/1348 [^]
(0155122)
guillermogil (manager)
2023-09-22 06:52

 Finally the problem was on the implementation of the provider for the customer.
It was receiving a list of properties (receipt among them) to use them for the processing of the payment and it was being returned on the resolve of the promise.

On the resolve it should be sent the object desired to be used and saved not all the entry parameters plus the new payment information.

- Issue History
Date Modified Username Field Change
2023-09-06 13:57 sofidossant New Issue
2023-09-06 13:57 sofidossant Assigned To => Retail
2023-09-06 13:57 sofidossant Triggers an Emergency Pack => No
2023-09-06 14:13 Practics Issue Monitored: Practics
2023-09-07 08:02 guillermogil Assigned To Retail => gaboflash
2023-09-15 00:48 hgbot Note Added: 0154873
2023-09-15 00:49 hgbot Note Added: 0154874
2023-09-15 00:49 hgbot Note Added: 0154875
2023-09-15 00:49 hgbot Note Added: 0154876
2023-09-18 06:10 guillermogil Note Added: 0154915
2023-09-18 06:10 guillermogil Status new => feedback
2023-09-18 06:12 hgbot Note Added: 0154916
2023-09-18 06:12 hgbot Note Added: 0154917
2023-09-18 06:12 hgbot Note Added: 0154918
2023-09-18 06:12 hgbot Note Added: 0154919
2023-09-19 06:05 guillermogil Assigned To gaboflash => sofidossant
2023-09-19 06:12 hgbot Note Added: 0154967
2023-09-22 06:48 hgbot Note Added: 0155121
2023-09-22 06:52 guillermogil Review Assigned To => guillermogil
2023-09-22 06:52 guillermogil Note Added: 0155122
2023-09-22 06:52 guillermogil Status feedback => closed
2023-09-22 06:52 guillermogil Resolution open => no change required

Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker