CORBA 2.3.3 Programmer's Guide for Java
The date and time of the event is given first. Because the log might contain many messages from a number of different
processes, examining EMS messages that were logged during a particular interval is a useful strategy. The second part
contains the text error message GIOP Proxy demarshal 0 profiles, which provides information that can
help you troubleshoot the problem.
Calling the Error Logging Facility
Each call to the error logging facility is made at one of four severity levels: Critical, Error, Warning, or Informational:
Critical indicates an error that could result in significant loss of, or damage to, your subsystems environment.●
Error indicates an error occurred that might require some user action to fix the problem (for example, a
configuration error).
●
Warning indicates an event occurred that might cause a problem in the future (for example, a database file is 90
percent full).
●
Informational messages are not error or warning related and can be used for instrumentation.●
When a call is made to log a message, the error logging facility must write the data to the log file before it can return to
the caller.
The error logging facility itself does not raise any exceptions or return any errors. If the error logging facility cannot
write to the error log file, it writes to the standard output (STDOUT).
You can log run-time exceptions by placing calls to the error logging facility in the error-handling routines of your
NonStop CORBA applications.
To ease the task of adding error-logging messages to your code, NonStop CORBA supplies several methods, one for
each severity level. When using these methods, you must supply the following information to each error-logging call
you make:
A unique error number that represents the error condition●
User-supplied error text●
Class name where the error was logged●
Line identifier where the error was logged●
Predefined Methods
To simplify the error-logging process, NonStop CORBA provides the following error-logging methods. See Error
Logging Example for an example of how you can use these methods.
/* Log message where severity = CRITICAL */
log_critical(java.lang.Class pp_src_class, int pv_src_line_num, int pv_err_num,
java.lang.String pp_text)
/* Log message where severity = ERROR */
log_error(java.lang.Class pp_src_class, int pv_src_line_num, int pv_err_num,
java.lang.String pp_text)
/* Log message where severity = WARNING */
log_warning(java.lang.Class pp_src_class, int pv_src_line_num, int pv_err_num,
java.lang.String pp_text)