My Oracle Support Banner

E1: XMLP: Badly Defined Printer Config Can Leak Table Handles in UBE and XMLP Kernels (Doc ID 2415763.1)

Last updated on NOVEMBER 22, 2019

Applies to:

JD Edwards EnterpriseOne Tools - Version 9.2 and later
Information in this document applies to any platform.


Symptom 1:

Open Cursor in the log.  An incorrectly defined printer, when used in a print request by XMLP kernel or UBE kernel, can cause the routine to exit without closing an open table handle to F986110, and in some cases, also leaves an empty temp file in the netTemporaryDir specified in the server's JDE.INI.

1. Define a printer with a valid paper type, and use a custom conversion string that is invalid.
2. Run a job using that printer.
3. When in 'D' status, print from WSJ.
4. Repeat
5. jdedebug.log will show, for the F986110 opens, the table handle count is growing.

Symptom 2:

Another symptom of this issue is, randomly the outstanding requests of the XMLP kernel will keep increasing.
Once it goes up to a certain level (Ex: 25-30), they will cause issues with XMLP jobs.

Ex: Users unable to open PDF output even though the PDF is generated successfully. And the status of the RD job in P95630 goes to "X" status




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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.