WebLogic

PDF Print E-mail
User Rating: / 4  |  Rate this article: PoorBest 

1. Server setup

Configuring WebLogic for monitoring can be done using the web bases Administration Console. To enable monitoring, you need to do the following:

  1. Create a user with membership in the Monitor or Admin groups.
  2. Enable IIOP.
  3. Restart server.

1.1. Create a user with membership in the Monitor or Admin groups

In the Administration Console, click Security Realms and then the realm that is set as default realm:

weblogic_securityRealms

Click Users and Groups and then make sure that the Users tab is selected. Create a new user (if you don't wish to use an existing user), and then click the user in the list.

weblogic_realm

Navigate to the Groups tab and make the user a member of the Monitors group, then click Save.

weblogic_userGroup

1.2. Enable IIOP

Click Servers and click the server that you want to monitor.

weblogic_servers

Go to the Protocols tab and then the IIOP tab. From there, make sure that Enable IIOP is checked:

weblogic_iiop

Click Save.

1.3. Restart server

For the changes to take effect, you need to restart the server.

2. LoadUI setup

Before starting monitoring WebLogic using LoadUI, library wlclient.jar must be copied to /ext folder (LoadUI must be restarted for changes to take effect). This library can be found in WebLogic installation folder …\Oracle\Middleware\wlserver_10.x\server\lib. When defining new WebLogic monitor in LoadUI, user must specify server host (in server definition screen) and port. Port is the WebLogic's listen port (defaults to 7001). Username and password are optional depending if authentication is required or not. You have to click Test connection to verify connection and retrieve the list of all available counters. Make sure that no firewall is blocking the port used in between the server and LoadUI.

3. Troubleshooting

If you are unable to connect, please try to set the default IIOP credentials and then restart the server:

weblogic_default_iiop

4. Available statistics

Server. Allows monitoring the open sockets for every server.

  • SocketsOpenedTotalCount. Total number of opened sockets for selected server.
  • OpenSocketsCurrentCount. Number of currently opened sockets for selected server.

Session. Allows monitoring session counters for every EAR and WAR deployed on a server.

  • OpenSessionsCurrentCount. Total number of currently opened sessions in a selected module.
  • OpenSessionsHighCount. Highest number of opened sessions in a selected module. The counter starts from zero every time the module is activated.
  • SessionsOpenedTotalCount. Total number of sessions opened in a selected module.

JDBC Connection Pool. Allows monitoring of JDBC connection pool counters. The counters are available at connection pool level.

  • ActiveConnectionsCurrentCount. Number of physical database connections in a selected connection pool.
  • WaitingForConnectionCurrentCount. Number of application requests currently waiting for a connection.
  • NumUnavailable. Number of connections currently unavailable because they are being tested or refreshed.
  • ActiveConnectionsAverageCount. Average number of active connections in the selected connection pool.
  • ConnectionDelayTime. Average time taken, in milliseconds, needed to create a physical database connection. The time is calculated as the sum of the time taken to create all physical database connections in the connection pool, divided by the total number of connections created.
  • ActiveConnectionsHighCount. Highest number of active database connections in the selected connection pool since it was instantiated. Active connections are connections in use by an application.
  • ConnectionsTotalCount. Total number of database connections created in the selected connection pool since it was instantiated.
  • CurrCapacity. Current number of database connections the selected connection pool (includes available connections, connections in use and connections unavailable).
  • FailuresToReconnectCount. Number of times the selected connection pool attempted to refresh a connection to a database and failed. This can occur when the database is down or due to network problems.
  • HighestNumUnavailable. Highest number of unavailable connections in the selected connection pool since it was instantiated.
  • WaitSecondsHighCount. Highest number of seconds an application waited for a connection from the selected connection pool since it was instantiated.
  • WaitingForConnectionHighCount. Highest number of application requests concurrently waiting for a connection from the selected connection pool.

JRockit. Allows monitoring the runtime counters of each JRockit Virtual Machine instance (only available when WebLogic is running in the JRockit Java Virtual Machine).

  • AllProcessorsAverageLoad. Average load of all host machine processors.
  • JvmProcessorLoad. The load of Java Virtual Machine on all host machine processors. When there's more then one processor exists on the host machine, this counter will give t he average value.
  • HeapFreeCurrent. Current available memory in Virtual Machine (in bytes).
  • HeapSizeCurrent. Current memory size of the Virtual Machine (in bytes).
  • FreeHeap. Amount of currently free memory of Java heap in Virtual Machine (in bytes).
  • UsedHeap. Amount of currently used memory of Java heap by the Virtual Machine (in bytes).
  • TotalHeap. Amount of heap memory, in bytes, currently allocated to the Virtual Machine.
  • FreePhysicalMemory. Amount of currently free physical memory on the host machine (in bytes).
  • UsedPhysicalMemory. Amount of currently used physical memory on the host machine (in bytes). The value represents the memory used by all processes on the machine, not just the JVM.
  • TotalPhysicalMemory. Amount of physical memory on the host machine. Swap or other types of virtual memory are not included in this value.
  • NumberOfDaemonThreads. Total number of daemon Java threads currently running in Virtual Machine in all processors.
  • NumberOfProcessors. Number of processors on computer where Java Virtual Machine is running. For systems that are not Symmetric Multi Processor (SMP), value will always be 1.
  • TotalGarbageCollectionCount. Number of garbage collection runs since the Virtual Machine was started.
  • TotalGarbageCollectionTime. Number of milliseconds spent on all garbage collection runs since the Virtual Machine was started.
  • TotalNumberOfThreads. Total number of Java deamon and non-deaemon threads currently running in the Virtual Machine. This is summary value for all processors.
  • TotalNurserySize. Amount of memory currently allocated to the nurseryn (in bytes). When non-generational garbage collector is in use thsi value is 0.

JVM. Allows monitoring JVM machine counters.

  • HeapFreeCurrent. Available memory in bytes for this Virtual Machine.
  • HeapSizeCurrent. Total memory size in bytes for this Virtual Machine.

Connector.

  • ConnectionPoolsTotalCount. Total size of the connection pool.
  • ConnectionPoolCurrentCount. Current size of the connection pool.

JMS Total. Allows monitoring JMS counters for all JMS Servers of the selected WebLogic server.

  • ConnectionsCurrentCount. Current number of connections to the selected JMS server.
  • ConnectionsHighCount. Highest number of connections to the selected JMS server since the last reset.
  • ConnectionsTotalCount. Total number of connections made to the selected JMS server since the last reset.
  • JMSServersCurrentCount. Current number of JMS servers deployed on this WebLogic Server instance.
  • JMSServersHighCount. Highest number of JMS servers deployed to the selected WebLogic Server instance since it has started.
  • JMSServersTotalCount. Total number of JMS servers deployed to the selected WebLogic Server instance since it has started.

JMS Servers. Allow monitoring each JMS Server on the selected WebLogic server.

  • DestinationsCurrentCount. Number of current destinations for the selected JMS server.
  • DestinationsHighCount. Highest number of destinations on the selected JMS server since the last reset.
  • DestinationsTotalCount. Number of destinations instantiated on the selected JMS server since the last reset.
  • MessagesCurrentCount. Number of messages currently stored on the selected JMS server. This number does not include the pending messages.
  • MessagesHighCount. Highest number of messages stored in the selected JMS server since the last reset.
  • MessagesPendingCount. Number of unacknowledged or uncommitted messages currently pending stored on the selected JMS server. Pending messages are over and above the current number of messages.
  • MessagesReceivedCount. Number of messages received on this destination since the last reset.
  • SessionPoolsCurrentCount. Number of session pools currently instantiated on the selected JMS server.
  • SessionPoolsHighCount. Highest number of session pools instantiated on the selected JMS server since the last reset.
  • SessionPoolsTotalCount. Number of session pools instantiated on the selected JMS server since the last reset.

JTA. Allows monitoring the transaction counters for the selected WebLogic server. All values are calculated per interval.

  • TransactionTotalCount. Total number of transactions processed by the selected server.
  • TransactionCommittedTotalCount. Total number of transactions committed by the selected server.
  • TransactionRolledBackTotalCount. Total number of transactions rolled back by the selected server.
  • TransactionRolledBackTimeoutTotalCount. Number of transactions rolled back by the selected server due to a timeout expiration.
  • TransactionRolledBackResourceTotalCount. Number of transactions rolled back by the selected server due to a resource error.
  • TransactionRolledBackAppTotalCount. Number of transactions rolled back by the selected server due to an application error.
  • TransactionRolledBackSystemTotalCount. Number of transactions rolled back by the selected server due to an internal system error.
  • TransactionHeuristicsTotalCount. Total number of transactions completed with a heuristic status.
  • TransactionAbandonedTotalCount. Total number of transactions abandoned by the selected server.
  • ActiveTransactionsTotalCount. Number of active transactions on the selected server.
  • SecondsActiveTotalCount. Average amount of time (in milliseconds) that transactions coordinated by the selected server have taken to commit.

Queue. Allows monitoring counters for each WebLogic Queue of the selected WebLogic Server.

  • PendingRequestCurrentCount. Number of waiting requests in the queue.
  • ExecuteThreadTotalCount. Total number of execute threads assigned to the queue.
  • ServicedRequestTotalCount. Number of requests that have been processed by the queue.
  • ExecuteThreadCurrentIdleCount. Number of idle threads assigned to the queue.

EJB Pool. Monitoring EJB instances for Entity Beans, MessageDriven Beans and Stateless Beans.

  • AccessTotalCount. Total number of times an attempt was made to get an instance from the free pool.
  • BeansInUseCurrentCount. Number of bean instances currently being used from the free pool.
  • DestroyedTotalCount. Total number of times a bean instance from this pool was destroyed due to a non-application exception being thrown from it.
  • MissTotalCount. Total number of times a failed attempt was made to get an instance from the free pool. An Attempt to get a bean from the pool will fail if there are no available instances in the pool.
  • PooledBeansCurrentCount. Number of currently available bean instances in the free pool.
  • TimeoutTotalCount. Total number of threads that have timed out waiting for an available bean instance from the free pool.
  • WaiterCurrentCount. Number of threads currently waiting for an available bean instance from the free pool.

EJB Transaction. Allows monitoring transaction counters for Entity Beans, MessageDriven Beans, Stateless Beans and Stateful Beans.

  • TransactionsCommittedTotalCount. Total number of transactions that have been committed for the selected EJB.
  • TransactionsRolledBackTotalCount. Total number of transactions that have been rolled back for the selected EJB.
  • TransactionsTimedOutTotalCount. Total number of transactions that have timed out for the selected EJB.

EJB Cache. Allows monitoring cache counters for Entity Beans and Stateful Beans.

  • ActivationCount. Total number of beans from the selected EJB that have been activated (beans that have been deserialized by the application server).
  • CacheAccessCount. Total number of attempts to access a bean from the cache.
  • CachedBeansCurrentCount. Total number of beans from the selected EJB currently in the EJB cache.
  • CacheMissCount. Total number of times an attempt to access a bean from the cache failed.
  • PassivationCount. Total number of beans from the selected EJB that have been passivated (beans that have been serialized by the application server).

Thread. Monitors thread pool information for the WebLogic Server.

  • CompletedRequestCount. Number of completed requests in the priority queue.
  • ExecuteThreadIdleCount. Number of idle threads in the pool. This count does not include standby threads and stuck threads. The count indicates threads that are ready to pick up new work when it arrives.
  • ExecuteThreadTotalCount. Total number of threads in the pool.
  • HoggingThreadCount. Number of threads that are being hogged by a request right now. These threads will either be declared as stuck after the configured timeout or will return to the pool before that. The self-tuning mechanism will backfill if necessary.
  • MinThreadsConstraintsCompleted. Number of requests with min threads constraint picked up out of order for execution immediately since their min threads requirement was not met. This does not include the case where threads are idle during schedule.
  • MinThreadsConstraintsPending. Number of requests that should be executed now to satisfy the min threads requirement.
  • PendingUserRequestCount. Number of pending user requests in the priority queue. The priority queue contains requests from internal subsystems and users. This is just the count of all user requests.
  • QueueLength. Number of pending requests in the priority queue. This is the total of internal system requests and user requests.
  • StandbyThreadCount. Number of threads in the standby pool. Surplus threads that are not needed to handle the present work load are designated as standby and added to the standby pool. These threads are activated when more threads are needed.
  • Throughput. Mean number of requests completed per second

Channel. This section allows the user to monitor the channels (network access points from the WebLogic Server). The counters are available for each channel.

  • AcceptCount. Number of sockets that have been accepted on this channel. This includes sockets both past and present so gives a good idea of the connection rate to the server.
  • ConnectionsCount. Number of active connections and sockets associated with this channel.
  • MessagesReceivedCount. Number of messages received on this channel.
  • MessagesSentCount. Number of messages sent on this channel.