Debug properties for OC4J configuration in OPMN managed environment

When OC4J is installed as a component of Oracle Application Server, OC4J system properties must be manually added to the opmn.xml configuration file. The file can be found at \opmn\conf directory. Options will be passed to managed OC4J instances at startup. Set Java system properties in the element where the id attribute is java-options. This element is enclosed within the subelement of the element in the XML structure. Preface all system properties with a -D. For example:

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

Debug Property and their Description

http.session.debug=
Provides information about HTTP session events to the console.

http.request.debug=
Provides information about each HTTP request to the console.

http.cluster.debug=
Provides information about HTTP clustering events to the console.

http.error.debug=
Prints all HTTP errors to the console.

http.method.trace.allow=
Enables the trace HTTP method.

datasource.verbose=
Provides verbose information on creation of data source and connections using data sources and connections released to the pool.

jdbc.debug=
Provides verbose information when JDBC calls are made.

ejb.cluster.debug=
Enables EJB clustering debug messages.

rmi.debug=
Prints RMI debug information to the console.

rmi.verbose=
Provides verbose information on RMI calls.

jca.connection.debug=
Provides extra diagnostic information for J2CA connections.

ws.debug=
Enables Web Services debugging.

Note : SOA Suite 10131 doc is the basis for the above doc. You can find more information @ http://download.oracle.com/docs/cd/B31017_01/web.1013/b28950/sysprops.htm

Cheers

Nirav