0039685: EDL Request Line Error Message length should be controlled when setting it

Anonymous | Login

Project:

News | My View | View Issues | Roadmap | Summary

View Revisions: Issue #39685		[ Back to Issue ]
Summary	0039685: EDL Request Line Error Message length should be controlled when setting it

Revision	2018-11-23 10:44 by caristu
Description	EDL Request Line Error Message length should be controlled when setting it. In case the error message provided is higher that the maximum allowed it can cause trouble when managing the error state of the request line. Because this can lead to have the import entry status in error and the related EDL request line status not being updated accordingly. This is a sample trace of an import entry error, caused because of trying to set an error message higher than the maximum allowed: org.openbravo.base.validation.ValidationException: errorMsg: <errorMsg> is too long, it has length <length>, the maximum allowed length is 2000 at org.openbravo.base.model.Property.checkIsValidValue(Property.java:833) at org.openbravo.base.structure.BaseOBObject.set(BaseOBObject.java:264) at org.openbravo.externaldata.integration.OBEDLRequestLine.setErrorMsg(OBEDLRequestLine.java:184) at org.openbravo.externaldata.integration.process.ProcessRequest.processRequestLine(ProcessRequest.java:513) at org.openbravo.externaldata.integration.process.EDLImportEntryProcessor$EDLEntryProcessRunnable.processEntry(EDLImportEntryProcessor.java:95) at org.openbravo.service.importprocess.ImportEntryProcessor$ImportEntryProcessRunnable.doRunCycle(ImportEntryProcessor.java:369) at org.openbravo.service.importprocess.ImportEntryProcessor$ImportEntryProcessRunnable.run(ImportEntryProcessor.java:290) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748)

Revision	2018-11-23 10:43 by caristu
Description	EDL Request Line Error Message length should be controlled when setting it. In case the error message provided is higher that the maximum allowed it can cause trouble when managing the error state of the request line. Because this can lead to have the import entry status in error and the related EDL request line status not being updated accordingly. This is a sample trace of an import entry error, caused because of trying to set an error message higher than the maximum allowed: org.openbravo.base.validation.ValidationException: errorMsg: <errorMsg> is too long, it has length 4398, the maximum allowed length is 2000 at org.openbravo.base.model.Property.checkIsValidValue(Property.java:833) at org.openbravo.base.structure.BaseOBObject.set(BaseOBObject.java:264) at org.openbravo.externaldata.integration.OBEDLRequestLine.setErrorMsg(OBEDLRequestLine.java:184) at org.openbravo.externaldata.integration.process.ProcessRequest.processRequestLine(ProcessRequest.java:513) at org.openbravo.externaldata.integration.process.EDLImportEntryProcessor$EDLEntryProcessRunnable.processEntry(EDLImportEntryProcessor.java:95) at org.openbravo.service.importprocess.ImportEntryProcessor$ImportEntryProcessRunnable.doRunCycle(ImportEntryProcessor.java:369) at org.openbravo.service.importprocess.ImportEntryProcessor$ImportEntryProcessRunnable.run(ImportEntryProcessor.java:290) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748)

Revision	2018-11-23 10:31 by caristu
Description	EDL Request Line Error Message length should be controlled when setting it. In case the error message provided is higher that the maximum allowed it can cause trouble when managing the error state of the request line. Because this can lead to have the import entry status in error and the related EDL request line status not being updated accordingly. This is a sample trace of an import entry error, caused because of trying to set an error message higher than the maximum allowed: org.openbravo.base.validation.ValidationException: errorMsg: <errorMsg> at org.openbravo.base.model.Property.checkIsValidValue(Property.java:833) at org.openbravo.base.structure.BaseOBObject.set(BaseOBObject.java:264) at org.openbravo.externaldata.integration.OBEDLRequestLine.setErrorMsg(OBEDLRequestLine.java:184) at org.openbravo.externaldata.integration.process.ProcessRequest.processRequestLine(ProcessRequest.java:513) at org.openbravo.externaldata.integration.process.EDLImportEntryProcessor$EDLEntryProcessRunnable.processEntry(EDLImportEntryProcessor.java:95) at org.openbravo.service.importprocess.ImportEntryProcessor$ImportEntryProcessRunnable.doRunCycle(ImportEntryProcessor.java:369) at org.openbravo.service.importprocess.ImportEntryProcessor$ImportEntryProcessRunnable.run(ImportEntryProcessor.java:290) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748)

Revision	2018-11-23 10:28 by caristu
Description	EDL Request Line Error Message length should be controlled when setting it. This can cause trouble when managing the error state of the request line. Because this can lead to have the import entry status in error and the related EDL request line status not being updated accordingly.

Revision	2018-11-23 10:26 by caristu
Description	Request Line Error Message length should be controlled when setting it. This can cause trouble when managing the error state of the request line. Because this can lead to have the import entry status in error and the request line status not being updated accordingly.