Category names map to the various subsystems of EAServer.
Different subsystems can use different category names for log messages,
and you can configure the output for each category. Table 3-13 lists the category
names used in EAServer. Many of these are not used in the preconfigured
log profiles, but you can add them.
Table 3-13: Log category names used in EAServer
Category name
|
Used by
|
|---|
<root>
|
N/A. This category is used as
the default parent for categories for which a parent category is
not specified.
|
axdisp
|
The ActiveX component dispatcher.
|
com.sybase
|
All EAServer internal subsystems that
do not specify another name.
|
com.sybase.CORBA
|
CORBA component dispatcher systems that
do not use another name.
|
com.sybase.CORBA.cts
|
Parent category for the following categories
that use this prefix in the name.
|
com.sybase.CORBA.cts.HeapStorage
|
The CtsComponents/HeapStorage storage
component that manages in-memory replication of EJB session bean
state and HTTP session state.
|
com.sybase.CORBA.cts.JdbcStorage
|
The CtsComponents/JdbcStorage storage
component that manages database storage of EJB CMP entity bean data,
EJB session bean state, and HTTP session state.
|
com.sybase.CORBA.cts.MessageService
|
The EAServer message service.
|
com.sybase.CORBA.cts.MessageService.
network
|
The EAServer message service, for debug
messages related to network connectivity (logged when the cms.debug.network message service
property is set to true).
|
com.sybase.CORBA.cts.MessageService.
session
|
The EAServer message service for messages
related to session connectivity (logged when the cms.debug.session message
service property is set to true).
|
com.sybase.CORBA.cts.ObjectCache
|
The object cache, which creates and manages
the caches used for servlet and JSP response caching and entity
component query and instance caching.
|
com.sybase.CORBA.cts.ThreadManager
|
The thread manager, which provides an
API to run components asynchronously.
|
com.sybase.CORBA.iiop
|
The Java client runtime IIOP subsystem,
for logging of errors.
|
com.sybase.CORBA.iiop.giop
|
The Java client runtime IIOP subsystem,
for logging of General Inter-Orb Protocol (GIOP) trace data (if
GIOP tracing is enabled).
|
com.sybase.CORBA.iiop.iiop
|
The Java client runtime IIOP subsystem,
for logging of IIOP trace data (if IIOP tracing is enabled).
|
com.sybase.CosNaming
|
The EAServer naming service.
|
com.sybase.CosNaming.console
|
The EAServer naming service, to output
messages to the console during server initialization. (You can override
the default destination so these messages do not go to the console.)
|
com.sybase.ejb.lwc
|
The EJB component lightweight container.
|
com.sybase.jaguar.deployment
|
The server-side deployment subsystem.
|
com.sybase.jaguar.importer
|
The client-side deployment subsystem
(used when importing J2EE archives, Java class and interface definitions,
and ActiveX interfaces among other things).
|
com.sybase.jaguar.jcm
|
The Java connection cache manager.
|
com.sybase.jaguar.jcm.cm
|
The Java connection cache manager, for
messages related to connector management.
|
com.sybase.jaguar.jcm.sm
|
The connection cache manager, for messages
related to security.
|
com.sybase.jaguar.management
|
Internal configuration management Java
classes.
|
com.sybase.jaguar.packager
|
The deployment subsystem, when exporting
J2EE archives.
|
com.sybase.jaguar.server
|
Server subsystems that don’t
use another name.
|
com.sybase.jaguar.server.cl
|
Server Java class loader.
|
com.sybase.jaguar.server.cl.copy
|
Server Java class loader, when creating
temporary copies of JAR files.
|
com.sybase.jaguar.server.hsb
|
Server hot standby system.
|
com.sybase.jaguar.servlet
|
The EAServer servlet engine.
|
com.sybase.jaguar.servlet,cl
|
The servlet engine class loader.
|
com.sybase.jaguar.servlet.hsc
|
The servlet engine HTTP session context
manager.
|
com.sybase.jaguar.servlet.security
|
The servlet engine security manager.
|
com.sybase.jms
|
The message service JMS API implementation.
|
libjagcm
|
Native connection cache manager.
|
libjcc
|
The C++ client runtime
implementation (used by C++, PowerBuilder, and
ActiveX clients as well as Java application clients that use the EAServer
SSL implementation).
|
libjdispatch
|
Native component dispatcher code.
|
libjdispatch.iiop
|
Server-side IIOP protocol handler code.
|
libjdispatch.iiop.read
|
Server-side IIOP protocol handler code,
read handling.
|
libjdispatch.iiops
|
Server-side IIOPS protocol handler code.
|
libjdispatch.management
|
Native code called from the management
API (for example, when restarting or refreshing the server).
|
libjdispatch.monitoring
|
Native code called from the monitoring
API.
|
libjdispatch.nip
|
Named instance pool implementation.
|
libjdispatch.nipmgr
|
Named instance pool manager.
|
libjdispatch.transaction
|
Native transaction manager code.
|
libjhttp.dynamo
|
PowerDynamo integration subsystem.
|
libjhttp.log
|
Native in-server HTTP protocol handler
code.
|
libjhttp.statlogger
|
Native in-server HTTP protocol handler
code, statistics provider implementation.
|
libjjdk12
|
The server subsystem that manages the
creation and configuration of the in-server Java VM.
|
libjots
|
Server-side object transaction service implementation.
|
srv_log
|
Output from the legacy logging methods
such as:
System.out.println or Jaguar.writeLog
from Java code running in the server
ErrorLogging.log from PowerBuilder
NVO components
JagLog from C or C++ components
IJagServer.writeLog from ActiveX
components
|
