My Oracle Support Banner

Failed To Obtain Debug Messages While Enable OC4J Debug Option In 10.1.3.x (Doc ID 1249404.1)

Last updated on OCTOBER 12, 2020

Applies to:

Oracle Containers for J2EE - Version to [Release AS10gR3]
Information in this document applies to any platform.


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 (
Title: Table 4-3 OC4J Debug Properties

For example debug settings in opmn.xml:

<ias-component id="default_group">
<process-type id="home" module-id="OC4J" status="enabled">
<category id="start-parameters">
     <data id="java-options" value="-Dhttp.session.debug=true......."/>

As expected result, the default_group~home~default_group~1 log under opmn/logs should then contain session debug messages for any session related events:

10/10/21 14:18:19 FINE: EvermindHttpServletRequest.unprivileged_getSession EvermindHttpServletRequest.getSession(), session=null
10/10/21 14:18:19 FINE: EvermindHttpServletRequest.unprivileged_getSession Requested Id is <ID>
10/10/21 14:18:19 FINE: HttpApplication.createSession Created session with id <SESSION_ID> at Thu Oct 21 14:18:19 EDT 2010, secureRequest: false
10/10/21 14:18:19 FINE: EvermindHttpSession.beginRequest EvermindHttpSession.beginRequest()
10/10/21 14:18:19 FINE: EvermindHttpSession.endRequest EvermindHttpSession.endRequest()
10/10/21 14:38:44 FINE: EvermindHttpSession.invalidate HTTP Session <SESSION_ID>.invalidate(), session was invalid:false
10/10/21 14:38:44 FINE: EvermindHttpSession.destroy Invalidating session with id <SESSION_ID> at Thu Oct 21 14:38:44 EDT 2010 (created at Thu Oct 21 14:18:19 EDT 2010) due to explicit invalidate() call
10/10/21 14:38:44 FINE: EvermindHttpSession.destroy Call stack of invalidate()java.lang.Throwable: invalidate() called

Those corresponding debug messages are not generated in the OC4J log after enabled the debug option.




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.