Command 'monitoring'

compared with
Version 7 by Victor NOËL
on Feb 15, 2016 11:05.

Key
This line was removed.
This word was removed. This word was added.
This line was added.

Changes (8)

View Page History
- mex-acceptor-thread-pool: Message exchange acceptor pool statistics
- mex-acceptor-working: Statistics about working message exchange acceptors
- mex-processor-object-pool: Message exchange processor object pool statistics
- mex-processor-thread-pool: Message exchange processor thread pool statistics
- incoming-http-requests-count: Counters of incoming HTTP requests
- mex-acceptor-thread-pool: Message exchange acceptor pool statistics
- mex-acceptor-working: Statistics about working message exchange acceptors
- mex-processor-object-pool: Message exchange processor object pool statistics
- mex-processor-thread-pool: Message exchange processor thread pool statistics
- local-transporter: Message exchange local transporter
- generic: Subscription to the defects of the CDK based component
- org.ow2.petals.component.framework.process.message.acceptor.pool.thread.dead: A message exchange acceptor thread is dead unexpectedly !
- org.ow2.petals.component.framework.process.message.processor.object.pool.exhausted: No more message exchange processor is available in the object pool to process message exchange !
- org.ow2.petals.component.framework.process.message.acceptor.pool.exhausted: No more thread is available to accept message exchange processor !
- org.ow2.petals.component.framework.process.message.processor.thread.pool.exhausted: No more thread is available to run a message exchange processor !
- petals-bc-soap: Subscription to the defects of the Petals BC SOAP
- org.ow2.petals.component.framework.process.message.acceptor.pool.thread.dead: A message exchange acceptor thread is dead unexpectedly !
- org.ow2.petals.component.framework.process.message.processor.object.pool.exhausted: No more message exchange processor is available in the object pool to process message exchange !
- org.ow2.petals.component.framework.process.message.acceptor.pool.exhausted: No more thread is available to accept message exchange processor !
- org.ow2.petals.component.framework.process.message.processor.thread.pool.exhausted: No more thread is available to run a message exchange processor !
| CDK-based component | [Message exchange acceptor thread pool|#message-exchange-acceptor-thread-pool] | {{-o generic -f mex-acceptor-thread-pool}} |
| CDK-based component | [Working message exchange acceptors|#working-message-exchange-acceptors] | {{-o generic -f mex-acceptor-working}} |
| CDK-based component | [Message exchange processor object pool|#message-exchange-processor-object-pool] | {{-o generic -f mex-processor-object-pool}} |
| CDK-based component | [Message exchange processor thread pool|#message-exchange-processor-thread-pool] | {{-o generic -f mex-processor-thread-pool}} |
| CDK-based component | [Service provider invocation number|#service-provider-invocations-count] | {{-o generic -f service-provider-invocations-count}} |
{code}

h3. {anchor:message-exchange-processor-object-pool}Message exchange processor object pool

Several metrics about the message exchange processor object pool of the component are available through the sub function '{{mex-processor-object-pool}}' of the monitored object '{{generic}}'. It's usage is:
{code}
-n <component-name>
{code}
where '{{<component-name>}}' is the unique name of the JBI component with which it was deployed.
Returned metrics are:
* {{BorrowedObjectsMax}}, the maximum number of borrowed objects,
* {{BorrowedObjectsCurrent}}, the current number of borrowed objects,
* {{IdleObjectsMax}}, the maximum number of idle objects,
* {{IdleObjectsCurrent}}, the current number of idle objects,
* {{MaxSize}}, the maximum size of the object pool,
* {{MinIdleSize}}, the minimum size of the object pool,
* {{Exhaustions}}, the number of exhaustions of the object pool.

{code}
> ./petals-cli.sh -h localhost -n 7700 -u petals -p petals -c -- monitoring -o generic -f mex-processor-thread-pool -- -n petals-bc-soap
BorrowedObjectsMax:50 BorrowedObjectsCurrent:0 IdleObjectsMax:8 IdleObjectsCurrent:8 MaxSize:50 MinIdleSize:10 Exhaustions:25535
{code}

h3. {anchor:message-exchange-processor-thread-pool}Message exchange processor thread pool

| {{org.ow2.petals.component.framework.process.message.acceptor.pool.thread.dead}} | A message exchange acceptor thread is dead unexpectedly ! |
| {{org.ow2.petals.component.framework.process.message.acceptor.pool.exhausted}} | No more thread is available to accept new message exchange ! |
| {{org.ow2.petals.component.framework.process.message.processor.object.pool.exhausted}} | No more message exchange processor is available in the object pool to process message exchange ! |
| {{org.ow2.petals.component.framework.process.message.processor.thread.pool.exhausted}} | No more thread is available to run a message exchange processor ! |
* {{petals-bc-soap}}, associated to the Petals BC SOAP, detects:
| {{org.ow2.petals.component.framework.process.message.acceptor.pool.thread.dead}} | A message exchange acceptor thread is dead unexpectedly ! |
| {{org.ow2.petals.component.framework.process.message.acceptor.pool.exhausted}} | No more thread is available to accept new message exchange ! |
| {{org.ow2.petals.component.framework.process.message.processor.object.pool.exhausted}} | No more message exchange processor is available in the object pool to process message exchange ! |
| {{org.ow2.petals.component.framework.process.message.processor.thread.pool.exhausted}} | No more thread is available to run a message exchange processor ! |
| {{org.ow2.petals.bc.soap.httpserver.threadpool.exhausted}} | No more thread is available in the HTTP thread pool to process incoming requests ! |