Failed To Obtain Debug Messages While Enable OC4J Debug Option In 10.1.3.x
(Doc ID 1249404.1)
Last updated on FEBRUARY 18, 2025
Applies to:
Oracle Containers for J2EE - Version 10.1.3.0.0 to 10.1.3.5.0 [Release AS10gR3]Information in this document applies to any platform.
Symptoms
OC4J debug options were enabled (see document section below) in OC4J java option, but it failed to generate the corresponding debug messages in the OC4J log file under opmn/logs directory. This issue only occurs in 10.1.3.x but not in earlier versions.
See debug options in
Oracle Containers for J2EE Configuration and Administration Guide
10g (10.1.3.1.0)
Title: Table 4-3 OC4J Debug Properties
https://download.oracle.com/docs/cd/B32110_01/web.1013/b28950/sysprops.htm#CHDFCCBF
10g (10.1.3.1.0)
Title: Table 4-3 OC4J Debug Properties
https://download.oracle.com/docs/cd/B32110_01/web.1013/b28950/sysprops.htm#CHDFCCBF
For example debug settings in opmn.xml:
Those corresponding debug messages are not generated in the OC4J log after enabled the debug option.
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 |