Martini Monitoring Threads
Martini is built to manage multi-threaded processes efficiently. You can monitor ongoing threads through the API Explorer and Server Admin UI.
Note
The Martini Server Runtime Admin UI is exclusively available in the Martini Server Runtime Edition.
Via the Server Admin UI
Access the Threads page by opening the Martini Server Runtime Admin UI in your browser. From the main menu, select Connections, then click Threads from the submenu.
This page lists all running threads and their states. Clicking on a thread name reveals an information panel with more details about the thread.
Via the API Explorer
Martini provides REST endpoints for retrieving thread information.
These API's enables you to:
- GET /esbapi/system/threads
: Retrieve a list of running threads
- GET /esbapi/system/threads/{id}
: Fetch detailed information about a thread
- GET /esbapi/system/threads/{id}/stacktrace
: View a thread's stack trace
Commonly Running Threads
Below are some of the threads you might encounter under Martini's thread monitoring interfaces:
Name | Description |
---|---|
[JMS_LISTENER] core/monitor-indexer-listener-1 |
Listens for JMS messages handling indexing of invoke documents. |
[JMS_LISTENER] core/monitor-listener-1 |
Listens for JMS messages handling storage of invoke documents. |
[JMS_LISTENER] core/tracker-index-listener-1 |
Listens for JMS messages handling indexing of Tracker documents. |
[JMS_LISTENER] core/tracker-listener-1 |
Listens for JMS messages handling storage of Tracker documents. |
ActiveMQ Broker[localhost] Scheduler |
Manages scheduling tasks within ActiveMQ broker. |
ActiveMQ BrokerService[localhost] Task-{n} |
Manages the lifecycle of an ActiveMQ broker. |
ActiveMQ Data File Writer |
Handles batch appends to a data file. |
ActiveMQ Journal Checkpoint Worker |
Worker for journal checkpointing. |
ActiveMQ Journal Scheduled executor |
Manages DataFiles in ActiveMQ Journal. |
ActiveMQ Session Task-2 |
Task runner for ActiveMQ connections. |
ActiveMQ Transport Server Thread Handler: {jms-url} |
Handles incoming Transport objects and delivers them asynchronously. |
ActiveMQ Transport Server: {jms-url} |
Manages incoming connections. |
ActiveMQ VMTransport: vm://localhost#{n}-{n} |
Handles messages sent synchronously and asynchronously. |
auth-provider-exec-0 |
|
bitronix-disk-force-batcher |
Executes disk force batches. |
bitronix-task-scheduler |
Timed task services. |
brokerChannel-{n} |
Handles messages to the broker from within the application. |
CaffeineCacheSessionRepository-cleanup-{n} |
Handles cleaning up of expired Sessions. |
Catalina-utility-{n} |
|
clientInboundChannel-{n} |
Handles messages from WebSocket clients. |
clientOutboundChannel-{n} |
Handles messages to WebSocket clients. |
Connection evictor |
Enforces an eviction policy for expired/idle persistent connections kept alive in the connection pool. |
DestroyJavaVM |
Unloads the Java VM on program exit. |
Finalizer |
Handles pulling of objects from the finalization queue and calls its finalize method. |
HSQLDB Timer @{n} |
Executes scheduled HSQLDB tasks. |
http-nio-9090-Acceptor |
Periodically checks that the connector is still accepting connections, also responsible for periodic checks of async timeouts. |
http-nio-9090-BlockPoller |
|
http-nio-9090-ClientPoller |
|
http-nio-9090-exec-{n} |
Processes incoming HTTP requests. |
IDE-{package-name} (index-thread-0) |
Handles indexing of files inside a package. |
JmsComponentManager (relay)-heartbeat-0 |
Periodically checks/transmits heartbeats between components. |
JmsComponentManager-consumer-0 |
Handles JMS messages. |
MessageBroker-{n} |
|
mysql-cj-abandoned-connection-cleanup |
Handles closing of abandoned MySQL connections. |
net.sf.ehcache.CacheManager@{n} |
Shutdown hook for the CacheManager. |
OkHttp ConnectionPool |
Manages reuse of HTTP and HTTP/2 connections for reduced network latency. |
OkHttp Dispatcher |
Policy on when async requests are executed. |
Okio Watchdog |
Handles timing out of blocking I/O. |
pool-1-integrate-l-thread-1 |
|
QuartzScheduler_QuartzSchedulerThread |
Responsible for performing the work of firing Triggers that are registered with the QuartzScheduler. |
QuartzScheduler_Worker-{n} |
Executes scheduled Quartz tasks. |
Reference Handler |
Enqueues pending References. |
searcherExecutor-{n}-thread-{n} |
|
service-reaper-{n} |
Handles termination of unused services. |
shutdown-thread-0 |
Listens for shutdown requests to terminate the instance. |
Signal Dispatcher |
Handles the native signals sent by the OS to the JVM. |
WatchKey[trackers.xml] |
Watches changes to the trackers.xml file. |
WebSocket background processing |
Processing mechanism for BackgroundProcess that triggers roughly once a second. |