You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Jerry Cwiklik (JIRA)" <de...@uima.apache.org> on 2017/08/17 13:14:00 UTC
[jira] [Created] (UIMA-5537) UIMA-DUCC: agent GC collector not
reporting GC stats
Jerry Cwiklik created UIMA-5537:
-----------------------------------
Summary: UIMA-DUCC: agent GC collector not reporting GC stats
Key: UIMA-5537
URL: https://issues.apache.org/jira/browse/UIMA-5537
Project: UIMA
Issue Type: Bug
Components: DUCC
Reporter: Jerry Cwiklik
Assignee: Jerry Cwiklik
Fix For: 2.2.1-Ducc
Agent's child process GC collector not reporting stats sometimes. When agent launches a child process it also starts a GC collector which probes the remote MBeanServer for current garbage collector stats. The remote process sends an update to the agent which includes process JMX port. This port is used by the GC collector to connect to the remote. There is a race here: an agent can start GC collector *before* it receives JMX port from the remote. The current code establishes JMX connection in its constructor which is a bug. If it fails to connect, it silently goes on and keeps reporting 0 for GC stats.
The fix is to improve logging to clearly identify what is happening. Since the collector is called on a timer, it should always check its connection and try to establish it if a previous attempt failed.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)