Index
Symbols
A
-
acquiring
-
acquiring logs of internal setup tool of virtual server manager and Server Communication Agent
-
Administration agent, Management agent, and Management Server log
-
analyzing
-
analyzing processing performance of Application Server using trace based performance analysis file
-
Application Server
C
-
classifications of functionality and corresponding manuals describing functionality
-
class-wise statistical information output by instance statistical functionality
-
class-wise statistical information output by reference-related information output functionality
-
class-wise statistical information output by STATIC member statistical functionality
-
collecting trace information of trace based performance analysis
-
collecting trace information of user-extended trace based performance analysis
-
configuration file for user-extended trace based performance analysis
-
configuration of user-extended trace based performance analysis
-
confirmation method of event log of Explicit Memory Management functionality
-
confirming
E
-
ejbserver.logger.channels.define.channel-name.filenum (batch server)
-
ejbserver.logger.channels.define.channel-name.filenum (J2EE server)
-
ejbserver.logger.channels.define.channel-name.filesize (batch server)
-
ejbserver.logger.channels.define.channel-name.filesize (J2EE server)
-
ejbserver.logger.channels.define.NIOHTTPAccessLogFile.filenum
-
ejbserver.logger.channels.define.NIOHTTPAccessLogFile.filesize
-
ejbserver.logger.channels.define.WebSocketAccessLogFile.filenum
-
ejbserver.logger.channels.define.WebSocketAccessLogFile.filesize
-
error in opening automatic allocation configuration file for explicit memory management
-
error in parsing automatic allocation configuration file for explicit memory management
-
event log of Explicit Memory Management functionality, [2], [3]
-
example of the filtered trace based performance analysis file collected in Application Server
-
example of the trace based performance analysis file collected in the Web server
-
example output
H
-
Hitachi Trace Common Library format log
I
-
identifying
-
identifying connection
-
if administration agent is terminated forcibly when OutOfMemoryError occurs
-
if problem occurs in node switching system for host unit management model
-
implementation for collection of root application information of trace based performance analysis
-
information on execution of Component Container Administrator setup command (in UNIX)
-
internal setup tool of virtual server manager and server communication agent logs
-
investigating
J
-
J2EE application
-
Java heap overflow in automatic release processing of explicit memory block
-
JavaVM message log
L
M
N
O
-
option to be specified for acquiring extended verbosegc information
-
output contents of message log indicating insufficient C heap
-
output destination of server management command log (Compatibility mode), [2]
-
output destinations and output methods of data required for troubleshooting
-
output format and output example of tenuring distribution information of Survivor area
-
output format and output items of access log of NIO HTTP Server
-
output trigger of event log of Explicit Memory Management functionality
-
overview of tenuring distribution information output functionality of Survivor area
-
overview of trace based performance analysis of applications
-
overview of trace based performance analysis of Application Server
-
overview of unused objects statistical functionality in tenured area
P
-
precaution
-
precaution when using tenuring distribution information output functionality of Survivor area
-
PRF daemon, [2], [3]
-
PRF trace collection levels (DB Connector for Cosminexus RM)
-
PRF trace collection levels (filter trace (when an exception occurs))
-
PRF trace collection levels (filter trace (when the processing terminates normally))
-
PRF trace collection levels (Message-driven Bean (EJB2.1 and later))
-
PRF trace collection levels (TP1 inbound integrated function)
-
PRF trace get level (execution functionality of batch application)
-
problem
R
-
recovering table for CMR
-
reference destination of methods for acquiring and investigating required data to be acquired
-
resource setting information
S
-
setting
-
settings for acquiring the event log of Explicit Memory Management functionality
-
settings for collecting snapshot log (systems for executing batch applications)
-
settings for collecting snapshot logs (systems for executing J2EE applications)
-
settings for methods to be traced by user-extended trace based performance analysis
-
settings for using user-extended trace based performance analysis
-
stack trace
-
statistic information for each class
-
system log of EJB client application
T
-
tenuring distribution information output functionality of Survivor area
-
trace collection points (filter trace (when an exception occurs))
-
trace collection points (filter trace (when the processing terminates normally))
-
trace collection points (Message-driven Bean (EJB2.1 and later))
-
trace collection points and PRF trace collection levels (database session failover functionality), [2], [3], [4]
-
trace collection points of batch application execution functionality
-
trace collection points of standard output, standard error output, and user log
-
trace collection points of Web container (trace of request processing)
-
trace collection points of Web container (trace of the database session failover functionality)
-
trace collection points when a J2EE server is started or terminated
-
trace get point (execution functionality of batch application)
-
trace information that can be collected (batch application execution functionality)
-
trace information that can be collected (CMT and TransactionManager)
-
trace information that can be collected (connection association)
-
trace information that can be collected (database session failover functionality), [2], [3], [4]
-
trace information that can be collected (DB Connector for RM)
-
trace information that can be collected (filter trace (when an exception occurs))
-
trace information that can be collected (filter trace (when the processing terminates normally))
-
trace information that can be collected (Message-driven Bean (EJB2.0))
-
trace information that can be collected (Message-driven Bean (EJB2.1 and later))
-
trace information that can be collected (Session Bean or Entity Bean)
-
trace information that can be collected (TP1 inbound integrated function)
-
trace information that can be collected (transaction timeout)
-
trace information that can be collected (Web container), [2]
-
trace information that can be collected (when the connection closes automatically)