LoggingΒΆ

Logging is enabled on the RMI server using Apache log4j. The logger is configured in bin/log4j.properties. The default configuration from the GUI installer creates one appender which is a rolling file log in log/rmi/rmi_server.log. The RMI server does not output by default to the console. This is easily changed by adding a console appender in the log4j configuration file. There is another available appender which logs messages of level INFO or higher to the Oracle table MESSAGE_TABLE (though connection errors obviously can’t be logged). This appender is defined within the code and is not user-configurable. It is disabled by default and can be enabled by editing the setting database.use_database_appender in the configuration file.

If the RMI server is being run as a service, standard output and standard error will be in the procrun log directory (logprocrun). If the runServer.sh command is used on Linux to start the RMI server, output will be directed to the file nohup.out.

Currently, Java in the Oracle JVM does not use log4j (though the classes have been loaded- future improvements may include log4j Oracle JVM logging).

Messages from the Oracle JVM can be found in the Oracle trace file. Alternatively, the SQL command:

CALL dbms_java.set_output(200000);

will direct Java output to sqlplus.

The PL/SQL functions and procedures print out various messages. To see them use:

set serveroutput on size 1000000

Note that Java and PL/SQL messages are buffered within SQL*Plus and are not available until an SQL command has completed.

Previous topic

Transactions

Next topic

RMI Networking