E1: XML: X0010GetNextNumber BSFN is Creating Manual Commit Database Calls Causing XML Interop Transactions to Leave Open DB Connections to Remain Open Locking the System
(Doc ID 2987425.1)
Last updated on SEPTEMBER 10, 2024
Applies to:
JD Edwards EnterpriseOne Tools - Version 9.2 and laterInformation in this document applies to any platform.
Symptoms
After uprading from 9.2.2.5 to 9.2.6.1, using XML Interop to create Sales Order with Transaction type, over time, DB connections continue to increase and do not clear unless End Session is called which clears the session and all the DB connections.
Steps to Duplicate
1. Create XML Transaction for Sales Order which calls BSFN X0010GetNextOrderNumber and call thru Interop
2. Monitor the COK over time and see that with only 1 connected user, the number of DB connections starts to increase causing dead lock in the database
3. XML Response to the transaction eventually returns "Dispatcher Time Out" error back to the calling party.
3. Only after sending End Session are all the DB connections cleared for the session which is not a normal process as this should happen thru the 'End Transaction' call.
Changes
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 |
| Changes |
| Cause |
| Solution |
| References |