CORBA 2.6 Programmer's Guide for C++
Process ID of the process that logged the error PId
Thread ID of the thread that logged the error TId
Exception type (not all log messages are associated with an exception) ExcptType
Exception name (not all exceptions are named) ExcptName
Name of source file that logged the error File
Line number of the source file that logged the error Line
While much of this information is composed by the error logging facility at the time the call is made, you must supply
some of it when you make your calls.
User-Supplied Information
When using the error logging facility to log run-time exceptions, you supply the following information in your calls to
the error logging API:
The unique error number that represents the error condition (a predefined application-error number between
7001 and 7100)
●
User-supplied error text●
A pointer to the CORBA::Environment object (optional)●
The name of the source file where the error occurred●
The line number of the source file where the error occurred●
System-Supplied Information
When a call is made to the error logging facility, NSDOM_Error_Log composes the date, time, process name,
process ID, thread ID, component ID, exception name (when supplied), error description, and error number for each
log message generated.
Starting a Separate EMS Collector for NonStop CORBA Messages
By default, NonStop CORBA EMS messages are sent to the system collector, $0. To specify a separate collector for
NonStop CORBA messages, you must first start up this new collector and then set the variable MY_COLLECTOR in
the $NSD_ROOT/etc/env.sh file to the new collector name.
For a particular application in a development environment, you might find it useful to use STDOUT or an OSS file for
the collector in your profile@ORB entity in the configuration database instead of using $0 as your collector. You'll
thus get all NonStop CORBA messages in one place, with simpler formatting. In a production environment, however,
you should send log messages to $0 (or STDCOLL).
Figure 51 shows a simplified diagram of the EMS layer on a NonStop system, its components, and its relationships to
the subsystem environment and operations environment. If NonStop CORBA is running, it would be one of the
subsystems.
Figure 5.1. EMS Collectors