E1: 41/42/43: No Timeout Message When Level 1 BSFN Exceeds Enterprise Server Timeout
(Doc ID 2261997.1)
Last updated on MAY 01, 2023
Applies to:
JD Edwards EnterpriseOne Procurement and Subcontract Management - Version 9.2 and laterJD Edwards EnterpriseOne Sales Order Management - Version 9.2 and later
JD Edwards EnterpriseOne Inventory Management - Version 9.2 and later
Information in this document applies to any platform.
Symptoms
On : 9.2 version, Inventory, Procurement, Sales
When running an application with Transaction Processing and calling a Level 1 BSFN from the OK Post Button Clicked Asynch event with TP active, no message is sent to the user if the BSFN processing time exceeds that of the enterprise sever timeout setting in the jas.ini. In addition no rollback command is issued to the database.
The end result to the user would appear be be lost transactions or missing transactions. For example a user may enter a sales order through P4210 or P42101, then at a later point discover that order is missing. A user may do a receipt in P4312 and discover at a later point the receipt is missing.
Applications that could be affected include P4112, P4113, P4114, P4210, P42101, P4205, P4310, P4312, and P4314. In addition this problem could cause the F41021 data to be incorrect. You may need to run the P42210 or R42210 to correct the F41021 data.
The issue is present in both 9.1.5.10 and 9.2.1.10 Tools releases. The issue does not occur in 9.1.4.7 and below. If you believe you are experiencing this issue look for the following message in the e1root.log. Note the BSFN name will vary depending on the app.
*ERROR* CallObject@43906fbb: COSE#1000 Request timeout: timeout after 90000ms host DNVMGSC54:6018(28764) SocID:41567 PID:4656 BSFN:F4312EndDoc user:TJ5903946 Env:JPD920
*ERROR* CallObject@43906fbb: The business function being executed is causing a problem user:TJ5903946 Env:JPD920
The user should should receive a message indicating the BSFN has timed out and the transaction was rolled back.
The issue can be reproduced at will with the following steps:
1) P4101\P41026. Create a new serial controlled item and set to 9 to assign serial number manually.
2) P4310. Enter a PO for 500 lines by importing data into the grid from excel with incremented serial numbers.
3) Server Manager. Log into Server Manager for the JAS instance and go to Network. Verify the timeout threshold is the default 90 seconds.
4) P4312. Inquire on the order and get ready to receive. Go back to Server Manager and turn on JAS logs for the user and debug logs for the call object kernel. This will slow down the process long enough for the process to time out. Click OK.
5) Wait 90 seconds and re-inquire on the order. Note it appears not to have been received. The user does not receive a timeout message that the transaction was rolled back.
6) P42210. Verify the F41021WF was left populated and the Post Commit Event never fired to rollback the records.
7) Using SQL Developer go into the F41021WF table and try and delete one of the records. The process will hang because the records are locked.
8) Review the e1root.log and note you can see the timeout message.
*ERROR* CallObject@43906fbb: COSE#1000 Request timeout: timeout after 90000ms host DNVMGSC54:6018(28764) SocID:41567 PID:4656 BSFN:F4312EndDoc user:TJ5903946 Env:JPD920
*ERROR* CallObject@43906fbb: The business function being executed is causing a problem user:TJ5903946 Env:JPD920
Review the jas log and you can see the MBF was called asynch but there was never a message the process timed out. Search for the Post Commit event and it cannot be found executing.
Review the debug logs and note the MBF was called with TP on and finished to completion. However there is no rollback of the transaction even though it timed out.
Example:
Starting Commit Point No : 1 for Transaction ID :
1737919242_4656_5044_535892620
COB00001: jdeCallObject called to launch F4312EndDoc.
Calling Business function F4312EndDoc from Level 1 for TJ5903946. Application
Name [P4312], Version [TCJ] (BSFNLevel = 1)
Return value is 0 for F4312EndDoc. (BSFNLevel = 1)
***There is no rollback command issued***
Due to this issue, users are losing transactions and do not get notified a problem has occurred. There are also locks that remain on various tables depending on the app. The locks occur because no rollback command was issued. Some customers have reported locks on F4105 and F46L001.
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 |