WebLogic Support in up.time

up.time enables you to monitor the performance and health of J2EE/Java applications that are running on a WebLogic server. up.time currently supports WebLogic on any platform.

You can now identify correlations between system performance and the J2EE application server, track end-user and database response times, and a number of other statistics for a WebLogic server. The diagram below shows how you can profile the many components of a J2EE environment and analyze the performance data to identify tuning opportunities, possible issues with application code, end-user response time problems, and database throughput.

Profiling components in a J2EE application

Performance Metrics

In addition to the WebLogic metrics that up.time collects, detailed system level performance metrics are also available. This enables you to analyze system compute performance, memory usage, disk and network performance, and then relate underlying system behavior to specific metrics within WebLogic. You can also use the information that up.time collects to generate reports that chart the historical performance of the server and the applications that are running on it.

Connection Pool Metrics

The following metrics contain performance information for connections to the JDBC data sources used by the WebLogic server:

  • FailuresToReconnectCount
    The number of times that the connection pool failed to reconnect to a data store.
  • ConnectionDelayTime
    The average time that was required to connect to a connection pool.
  • ActiveConnectionsCurrentCount
    The current number of active connections in a JDBC connection pool.
  • ActiveConnectionsHighCount
    The highest number of active connections in a JDBC connection pool.
  • LeakedConnectionsCount
    The total number of connections that have been checked out of, but not returned to, the connection pool.
  • CurrCapacity
    The current number of database connections in the JDBC connection pool.
  • NumAvailable
    The number of available sessions in the session pool that are not currently being used.
  • WaitingForConnectionCurrentCount
    The current number of requests that are waiting for a connection to the connection pool.

Enterprise JavaBean Metrics

The following metrics contain information about the Enterprise JavaBeans (EJBs) that are running on the WebLogic server:

  • AccessTotalCount
    The total number of times an attempt was made to get an EJB instance from the free pool.
  • BeansInCurrentUseCount
    The number of EJB instances in the free pool which are currently in use.
  • CachedBeansCurrentCount
    The total number of EJBs that are in the execution cache.
  • ActivationCount
    The number of EJBs that have been activated.
  • PassivationCount
    The total number of EJBs that have been removed from the execution cache.
  • CacheAccessCount
    The total number of that an attempt was made to access an EJB from the execution cache.
  • CacheMissCount
    The total number of times that an attempt to access an EJB from the execution cache failed.

Other Metrics

The following metrics contain information about the Java Virtual Machine (JVM), connections, requests, transactions, and servlets that are associated with the WebLogic server:

  • HeapSizeCurrent
    The amount of memory, in bytes, that is in the WebLogic server's JVM heap.
  • HeapFreeCurrent
    The current amount of free memory, in bytes, that is in the WebLogic server's JVM heap.
  • OpenSocketsCurrentCount
    The current number sockets on the server that that are open and receiving requests.
  • AcceptBacklog
    The number of requests that are waiting for a TCP connection.
  • ExecuteThreadCurrentIdleCount
    The number of threads in the server's execution queue that are idle or which are not being used to process data.
  • PendingRequestCurrentCount
    The number of pending requests that are in the server's execution queue.
  • TransactionCommittedTotalCount
    The total number of transactions that have been processed by the WebLogic server.
  • TransactionRolledBackTotalCount
    The total number of transactions that have been rolled back.
  • InvocationTotalCount
    The total number of times that a servlet running on the WebLogic server was invoked.