Mailing-List: contact user-help@uima.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@uima.apache.org
MIME-Version: 1.0
In-Reply-To: <CAB3DYDq=ogx+O-gjqsTS-Z67QRSkLzXw3S89YFBbwrD6Kzj9hQ@mail.gmail.com>
References: <CAB3DYDq=ogx+O-gjqsTS-Z67QRSkLzXw3S89YFBbwrD6Kzj9hQ@mail.gmail.com>
From: Jaroslaw Cwiklik <uimaee@gmail.com>
Date: Fri, 23 Dec 2016 09:20:49 -0500
Message-ID: <CAO329yCr=YH_jnLiHtOwZUR5e5ZFLKwCEsG22d=cmrzTL2f5Ww@mail.gmail.com>
Subject: Re: Using optional argument -Duima.as.enable.jmx=false
To: user@uima.apache.org
Content-Type: multipart/alternative; boundary=001a114b07e4c0ba2505445417ce
archived-at: Fri, 23 Dec 2016 14:21:00 -0000

--001a114b07e4c0ba2505445417ce
Content-Type: text/plain; charset=UTF-8

Nelson, thanks for pointing this out. This parameter
(-Duima.as.enable.jmx=false)
disables ActiveMQ JMX port when running UIMA-AS extended tests. Per JIRA
https://issues.apache.org/jira/browse/UIMA-5166 the fix addresses this
scenario only. The fix was motivated by a complaint from Apache infra team
which noticed an open RMI port while running UIMA-AS Jenkins regression
tests.

The UIMA-AS 2.9.0 README comments are misleading and suggest that this flag
can disable JMX port of the service.I need to rewrite the comment to
reflect the truth. Will open JIRA for this.

As far as I know there is no way in java code to override these

 -Dcom.sun.management.jmxremote
-Dcom.sun.management.jmxremote.port=$PORT
-Dcom.sun.management.jmxremote.authenticate=false
-Dcom.sun.management.jmxremote.ssl=false

These settings take effect before the jvm hands off control to a user code.
The java JMX Agent's registry which opens the port is not
accessible for the purpose of stopping the port once it is started. So
bottom line the comments are wrong and need to be fixed. I will address
this soon. To manage service jmx port use the above 4 -Dcom.sun.management..
 settings

- Jerry Cwiklik


With the above there is no way to disable the RMI port as far as I know.
The -D's are

On Thu, Dec 22, 2016 at 2:49 PM, nelson rivera <nelsonrivera12@gmail.com>
wrote:

> I am testing recent uima-as 2.9.0 release. I try deploy a service
> uima-as, with the new argument uima.as.enable.jmx with value "false",
> i expected that the UIMA-AS will start with no JMX support and no port
> will not be opened, but a port continue opening and Providing JMX
> statistics of processing.
>
> What should be the behavior of this argument?
>
> This is the complete set of arguments JMX configured in the uima-as
> service start:
>
> -Duima.as.enable.jmx=false
> -Duima.as.enable.jmx=false -Dcom.sun.management.jmxremote
> -Dcom.sun.management.jmxremote.port=$PORT
> -Dcom.sun.management.jmxremote.authenticate=false
> -Dcom.sun.management.jmxremote.ssl=false
>

--001a114b07e4c0ba2505445417ce--