Directory Server Connection Pool Log
The user management engine (UME) can use a directory server as a data source. The UME accesses the directory server through a number of connections in a connection pool. The directory server connection pool log takes a snapshot of the connections in the connection pool, reporting their state: idle or in use . You can configure how often the system records the state of the connections. The UMEcreates a separate log for each connection pool. There is a connection pool for each object class configured.
You can use the directory server connection pool log to monitor how the directory server connections in the pool are being used. This enables you to troubleshoot connection problems and optimize performance.
To enable the directory server connection pool log, configure the setting Monitoring Interval. For more information, see Configuring the UME to Use an LDAP Directory as Data Source .
This log does not have a maximum file size. Disable the log when you no longer need it.
To view the log files, use any text editor.
When enabled, the UME creates the directory server connection pool log file, sapum_cpmon_<hostname>_<port>_<object_ID>.log , in the following location:
<drive:>\usr\sap\<SID>\<instance>\j2ee\cluster\server<n>
The file name uses the following syntax:
sap.um_cpmon_<hostname>_<port>_<objectID>.log
Hostname and port refer to the directory server. Object ID refers to the object class; the default values are GRUP , UACC , and USER .
When you start the SAP NetWeaver Application Server (AS) Java, the system overwrites the log files.
Directory Server Collection Pool Log Fields
| Field | Description |
|---|---|
|
Time stamp |
Time and date the log entry was made. |
|
Open connections |
Number of connections in the connection pool. |
|
Used connections |
Number of connections in the connection pool that are currently in use. |
|
Idle connections |
Number of connections in the connection pool that are idle. |
|
Waiting threads |
Number of threads waiting for a connection. |
You can also monitor access to the directory server. For more information, see Directory Server Access Log .
Below is an example of the log output:
Jndi connection pool status for pool Time / open connections / used connections / idle connections / waiting threads 02.12.2005 10:39:16.100: 1 0 1 0 02.12.2005 10:39.18.102: 1 0 1 0