Montag, Januar 17, 2005
OC4J Debuglevel
-verbosity is my favorite OC4J startparameter to get OC4J debug output. The range is defined from 1-10:
$JAVA_HOME/java -jar oc4j.jar -verbosity 10
Today I need a additional parameter to get more information about the used DataSource:
java -Ddatasource.verbose=true -Dhttp.session.debug=true -jar oc4j.jar -verbosity
HTTP Debugging
- http.session.debug = Provides information about HTTP session events
- http.cluster.debug = Provides information about HTTP clustering events
- http.error.debug = Prints all HTTP errors
JDBC Debugging
- datasource.verbose = Provides verbose information on creation of data source and connections using Data Sources and connections released to the pool, etc,
- jdbc.debug = Provides very verbose information when JDBC calls are made
EJB Debugging
- ejb.cluster.debug = Turns on EJB clustering debug messages
- transaction.debug = Provides debug information on transactions, useful for JTA debugging
RMI Debugging
- rmi.debug = Prints RMI debug information
- rmi.verbose = Provides very verbose information on RMI callsJMS Debugging
- jms.debug = Prints JMS debug information
http://www.oracle.com/technology/tech/java/oc4j/htdocs/oc4j-logging-debugging-technote.html
