Performance Issue with Issue Allocation Saved Query and Other Recurring Process Saved Queries
(Doc ID 451951.1)
Last updated on JULY 20, 2024
Applies to:
Oracle Transportation Management - Version 5.0 and laterInformation in this document applies to any platform.
Symptoms
-- Problem Statement:
On 5.0, When attempting to run a recurring process that sends an output of a query to an external system, the following error occurs:
ERROR
java.sql.SQLException: The transaction is no longer active - status: 'Marked rollback.
[Reason=weblogic.transaction.internal.TimedOutException: Transaction timed out after 299 seconds
-- Steps To Reproduce:
The issue can be reproduced at random with the following steps:
1. Set up a recurring process for Issue Allocation with Allocation Type of Planning and send the output to an External System via HTTPPOST
2. Watch the result of the recurring process
3. The recurring process errors occassionally with the error,
java.sql.SQLException: The transaction is no longer active - status: 'Marked rollback.
[Reason=weblogic.transaction.internal.TimedOutException: Transaction timed out after 299 seconds
-- Business Impact:
The issue has the following business impact:
Due to this issue, Allocation records are not being notified to the external system causing delays in financials reporting
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 |
| This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review. |