Incorrect Submitted Date Set When E2B Transmission Has Errors in Axway
(Doc ID 2941020.1)
Last updated on JANUARY 02, 2025
Applies to:
Oracle Life Sciences Argus Safety - Version 8.2.2 to 8.4.3.2 [Release 8.2 to 8.4]Information in this document applies to any platform.
Symptoms
If there were some errors on Axway while transmitting E2B, Axway produced the report twice with the "Messaging.Message.Producing" message.
This report was eventually transmitted to the reporting destination via Axway and received the ACK.
In this case, GMT conversion happens twice resulting in an incorrect date for CMN_REG_REPORTS.DATE_SUBMITTED and also EDI_INFO.EDI_COMPLETE_DATE.
Steps:
1. Transmitted E2B from Argus
2. ESM generated the report
3. Some issue/error occurred while transmitting the report to the reporting destination on Axway
4. Report was transmitted to reporting destination
5. ACK file received and imported into Argus
6. GMT conversion happened twice resulting in an incorrect submitted date being set for this report
For example #1 : "Messaging.Message.Interrupted" occurred on Axway while transmitting the report.
The following records are stored in the Relsysargus table.
| EVENT ----------------------------------------------- |
EVENT_DATE -------------------------------------------- |
| Messaging.Message.MessagePickup | 1/9/2023 10:03:41 |
| Messaging.Message.MessageReceived | 1/9/2023 10:03:41 |
| Messaging.Message.MessageUnpackaged.Request | 1/9/2023 10:03:41 |
| Messaging.Message.MessagePackaged.Request | 1/9/2023 10:03:41 |
| Messaging.Message.Producing | 1/9/2023 10:03:41 <---- 1st Producing |
| Messaging.Message.Interrupted | 1/9/2023 10:04:11 <-------------- Interrupted |
| Messaging.Message.Producing | 1/9/2023 10:09:11 <---- 2nd Producing |
| Messaging.Message.MessageSent | 1/9/2023 10:09:12 |
| Messaging.Message.PayloadDelivered | 1/9/2023 10:09:12 |
The delivered date shows as "1/9/2023 10:09".
The submitted date of the report (such as CMN_REG_REPORTS.DATE_SUBMITTED) is a GMT field. All Argus servers timezone are set as PST (GMT - 8 hours) for example.
Thus the delivered date "1/9/2023 10:09 " plus 8 hours which is "1/9/2023 18:09" is supposed to be set as the submitted date after GMT conversion.
However, GMT conversion was performed twice because Axway had "Messaging.Message.Producing" twice due to "Messaging.Message.Interrupted".
Therefore, the delivered date"1/9/2023 10:09" plus 8 hours plus another 8 hours (total 16 hours added by GMT conversion) which is "1/10/2023 2:09" was set as the submitted date.
Note:
1. Axway log shows the following timeout error while the issue occurred on Axway.
com.cyclonecommerce.tradingengine.transport.UnableToProduceException: java.net.SocketTimeoutException: HTTP response timeout exceeded: 30s; partner's server may be experiencing problems: Socket[addr=xxx.xxx.xxx/xxx.xxx.xxx.xx,port=xxx,localport=xxx]; java.net.SocketTimeoutException: Read timed out
at com.cyclonecommerce.tradingengine.transport.http.HttpClientBase.send(HttpClientBase.java:364) ~[interchange-server.jar:xx.4.0-2]
at com.cyclonecommerce.tradingengine.transport.system.production.producers.HttpProducer.send(HttpProducer.java:203) ~[interchange-server.jar:xx.4.0-2]
at com.cyclonecommerce.tradingengine.transport.system.production.producers.HttpProducer.produce(HttpProducer.java:74) ~[interchange-server.jar:xx.4.0-2]
at com.cyclonecommerce.tradingengine.transport.system.production.ProducerTask.produce(ProducerTask.java:326) [interchange-server.jar:xx.4.0-2]
at com.cyclonecommerce.tradingengine.transport.system.production.ProducerTask.executeImpl(ProducerTask.java:181) [interchange-server.jar:xx.4.0-2]
at com.cyclonecommerce.tradingengine.transport.system.production.ProducerTask.execute(ProducerTask.java:144) [interchange-server.jar:xx.4.0-2]
at com.cyclonecommerce.util.task.TaskScheduler$WorkerThread.primRun(TaskScheduler.java:457) [interchange-server.jar:xx.4.0-2]
at com.axway.cluster.extensions.thread.EventedThread.run(EventedThread.java:81) [interchange-threads.jar:xx.4.0-2]
Caused by: java.net.SocketTimeoutException: HTTP response timeout exceeded: 30s; partner's server may be experiencing problems: Socket[addr=xx.xxx.xx/xxx.xxx.xxx.xx,port=xxxx,localport=xxxx]; java.net.SocketTimeoutException: Read timed out
at com.cyclonecommerce.tradingengine.transport.http.HttpResponseReader.read(HttpResponseReader.java:539) ~[interchange-server.jar:xx.4.0-2]
at com.cyclonecommerce.tradingengine.transport.http.HttpResponseReader.readLine(HttpResponseReader.java:477) ~[interchange-server.jar:xx.4.0-2]
at com.cyclonecommerce.tradingengine.transport.http.HttpResponseReader.skipIntermediateResponses(HttpResponseReader.java:184) ~[interchange-server.jar:xx.4.0-2]
at com.cyclonecommerce.tradingengine.transport.http.HttpResponseReader.readResponse(HttpResponseReader.java:150) ~[interchange-server.jar:xx.4.0-2]
at com.cyclonecommerce.tradingengine.transport.http.HttpClientBase.readResponse(HttpClientBase.java:913) ~[interchange-server.jar:xx.4.0-2]
at com.cyclonecommerce.tradingengine.transport.http.HttpClientBase.retrieveResponse(HttpClientBase.java:710) ~[interchange-server.jar:xx.4.0-2]
at com.cyclonecommerce.tradingengine.transport.http.HttpClientBase.send(HttpClientBase.java:355) ~[interchange-server.jar:xx.4.0-2]
... 7 more
2. ESM_GatewayStatusCheck log file shows the following log while the issue occurred on Axway.
09-Jan-2023 10:06:31 AM DEFAULT: Error occurred in Update_EDI_Info Fn. Contact your system administrator
For example #2 : "Messaging.Message.MessageIgnored" occurred on Axway while transmitting the report.
The following records are stored in the Relsysargus table.
| EVENT ----------------------------------------------- |
EVENT_DATE -------------------------------------------- |
| Messaging.Message.MessagePickup | 12/02/2022 10:09:01 |
| Messaging.Message.MessageReceived | 12/02/2022 10:09:01 |
| Messaging.Message.MessageUnpackaged.Request | 12/02/2022 10:09:01 |
| Messaging.Message.MessagePackaged.Request | 12/02/2022 10:09:01 |
| Messaging.Message.Producing | 12/02/2022 10:09:01 <---- 1st Producing |
| Messaging.Message.MessageSent | 12/02/2022 10:09:02 <---- 1st Sent |
| Messaging.Message.MessageReceived | 12/02/2022 10:09:02 |
| Messaging.Message.MessageIgnored | 12/02/2022 10:09:02 <----------------- Ignored |
| Messaging.Message.ResendInitiated | 12/02/2022 11:09:02 |
| Messaging.Message.Producing | 12/02/2022 11:09:02 <---- 2nd Producing |
| Messaging.Message.MessageSent | 12/02/2022 11:09:03 <---- 2nd Sent |
| Messaging.Message.MessageReceived | 12/02/2022 11:09:03 |
| Messaging.Message.MessageIgnored | 12/02/2022 11:09:03 |
| Messaging.Message.PayloadDelivered | 12/02/2022 11:09:12 |
| Messaging.Message.ResponseDelivered | 12/02/2022 11:09:12 |
The delivered date shows as "12/2/2022 11:09".
The submitted date of the report (such as CMN_REG_REPORTS.DATE_SUBMITTED) is a GMT field. All Argus servers timezone are set as PST (GMT - 8 hours) for example.
Thus the delivered date "12/2/2022 11:09 " plus 8 hours which is "12/2/2022 19:09" is supposed to be set as the submitted date after GMT conversion.
However, GMT conversion was performed twice because Axway had "Messaging.Message.Producing" twice due to "Messaging.Message.MessageIgnored".
Therefore, the delivered date"12/2/2022 11:09" plus 8 hours plus another 8 hours (total 16 hours added by GMT conversion) which is "12/3/2022 3:09" was set as the submitted date.
Another scenario:
If no record exists in the <Axway_schema>.relsysargus table for the report (E2B/ACK) transmission, system will check the messages.DELIVEREDTIME in <axway_schema>.messages table and retrieve the MDN details and then place the MDN Date/time as submitted date.
However, system did the double conversion to this MDN date/time so that system added another GMT conversion (between sever timezone and GMT) against messages.DELIVEREDTIME.
This is why the incorrect date after the double conversion was set in the submitted date.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |
| References |