uima-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jerry Cwiklik (JIRA)" <...@uima.apache.org>
Subject [jira] [Closed] (UIMA-2395) UIMA AS service not logging a msg about missing JMX property
Date Thu, 03 May 2012 18:28:51 GMT

     [ https://issues.apache.org/jira/browse/UIMA-2395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jerry Cwiklik closed UIMA-2395.
-------------------------------

    Resolution: Fixed

Modified to log a message about missing jmx property and exit the jvm if a user intended to
start a service with JMX monitor but not provided jmx port
                
> UIMA AS service not logging a msg about missing JMX property
> ------------------------------------------------------------
>
>                 Key: UIMA-2395
>                 URL: https://issues.apache.org/jira/browse/UIMA-2395
>             Project: UIMA
>          Issue Type: Bug
>          Components: Async Scaleout
>            Reporter: Jerry Cwiklik
>            Assignee: Jerry Cwiklik
>            Priority: Minor
>             Fix For: 2.4.0AS
>
>
> UIMA AS service wrapper doesn't log a msg when it detects missing jmx monitor property.
The service simply starts with no hint of misconfiguration. The jmx monitor is optional, but
requires two parameters: the rate at which to collect stats and jmx port of the monitored
service. The latter is specified via -Dcom.sun.management.jmxremote.port=xxx property. If
omitted, UIMA AS service wrapper just proceeds as if the jmx monitor was *not* requested by
a user. Modify code to log a message indicating that the jmx port is missing and exit the
process. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message