Configuring Engine Tier Caching Monitoring and Tuning Cache Performance

Configuring SIP Data Tier Partitions and Replicas 6-23 When enabled, the size of the cache is fixed at 250 call states. Because the cache consumes memory, you may need to modify the JVM settings used to run engine tier servers to meet your performance goals. Cached call states are maintained in the tenured store of the garbage collector. Try reducing the fixed NewSize value when the cache is enabled for example, -XX:MaxNewSize=32m -XX:NewSize=32m. Note that the actual value depends on the call state size used by applications, as well as the size of the applications themselves.

6.8 Monitoring and Troubleshooting SIP Data Tier Servers

A runtime MBean, ReplicaRuntimeMBean, provides valuable information about the current state and configuration of the SIP data tier. See Oracle Fusion Middleware Communication Services Java API Reference for a description of the attributes provided in this MBean. Many of these attributes can be viewed using the SIP Servers Monitoring Data Tier Information tab in the Administration Console, as shown in Figure 6–6 . Figure 6–6 SIP Data Tier Monitoring in the Administration Console Example 6–8 shows a simple WLST session that queries the current attributes of a single Managed Server instance in a SIP data tier partition. Table 6–1 describes the MBean services in more detail. Table 6–3 SipPerformanceRuntime Attribute Summary Attribute Description cacheRequests Tracks the total number of requests for session data items. cacheHits The server increments this attribute each time a request for session data results in a version of that data being found in the engine tier servers local cache. Note that this counter is incremented even if the cached data is out-of-date and needs to be updated with data from the SIP data tier. cacheValidHits This attribute is incremented each time a request for session data is fully satisfied by a cached version of the data. 6-24 Oracle WebLogic Communications Server Administration Guide Example 6–8 Displaying ReplicaRuntimeMBean Attributes connectweblogic,weblogic,t3:datahost1:7001 custom cdcom.bea cdcom.bea:ServerRuntime=replica1,Name=replica1,Type=ReplicaRuntime ls -rw- BackupStoreInboundStatistics null -rw- BackupStoreOutboundStatistics null -rw- BytesReceived 0 -rw- BytesSent 0 -rw- CurrentViewId 2 -rw- DataItemCount 0 -rw- DataItemsToRecover 0 -rw- DatabaseStoreStatistics null -rw- HighKeyCount 0 -rw- HighTotalBytes 0 -rw- KeyCount 0 -rw- Name replica1 -rw- Parent com.bea:Name=replica1,Type=S erverRuntime -rw- PartitionId 0 -rw- PartitionName part-1 -rw- ReplicaId 0 -rw- ReplicaName replica1 -rw- ReplicaServersInCurrentView java.lang.String[replica1, replica2] -rw- ReplicasInCurrentView [I75378c -rw- State ONLINE -rw- TimerQueueSize 0 -rw- TotalBytes 0 -rw- Type ReplicaRuntime Table 6–4 ReplicaRuntimeMBean Method and Attribute Summary MethodAttribute Description dumpState Records the entire state of the selected SIP data tier server instance to the Oracle WebLogic Communication Services log file. You may want to use the dumpState method to provide additional diagnostic information to a Technical Support representative in the event of a problem. BackupStoreInboundStatistics Provides statistics about call state data replicated from a remote geographical site. BackupStoreOutboundStatistics Provides statistics about call state data replicated to a remote geographical site. BytesReceived The total number of bytes received by this SIP data tier server. Bytes are received as servers in the engine tier provide call state data to be stored. BytesSent The total number of bytes sent from this SIP data tier server. Bytes are sent to engine tier servers when requested to provide the stored call state.