You can also use the management API over messaging. Take a look at a
class named SimpleManagement on the codebase in main.
I know how to do JMX and stuff but I find it easier to manage.
On Thu, Aug 31, 2023 at 9:46 AM Justin Bertram <jbert...@apache.org> wrote:
> The default management.xml does indeed have the connector commented out
> which means there is no remote JMX connectivity. This is for security
> purposes so that it's less likely that someone deploys an unsecured broker
> with management wide open.
>
> Therefore, if you want to enable remote JMX connectivity you need to enable
> the connector.
>
>
> Justin
>
>
> On Thu, Aug 31, 2023 at 8:20 AM Sargrad, Dave <dave.sarg...@saabinc.com>
> wrote:
>
> > Looking at the referenced documentation, I see that the proper way to set
> > the JMX connection port is as follows:
> > <connector connector-port="1099"/>
> >
> > Our current management.xml does not specify this connector-port (it is
> > commented out).
> > <!--<connector connector-port="1099"/>-->
> >
> > What is the default port? This is not jumping out at me in the referenced
> > documentation?
> >
> >
> >
> >
> > This message is marked Public.
> >
> > -----Original Message-----
> > From: Justin Bertram <jbert...@apache.org>
> > Sent: Wednesday, August 30, 2023 12:50 PM
> > To: users@activemq.apache.org
> > Subject: Re: FW: {EXTERNAL MAIL} WELCOME to users@activemq.apache.org
> >
> > The "client-kickoff" example is using Java system properties to configure
> > remote JMX connectivity. However, that configuration method was replaced
> > awhile back with management.xml which you can see being used in the "jmx"
> > example. I've opened ARTEMIS-4409 [1] and sent a PR to fix this. In the
> > meantime, please refer to the "jmx" example as well as the documentation
> > [2] for details on how remote JMX connectivity should be configured.
> >
> > The management API is fundamentally based on JMX, but it is exposed in
> > several different ways as noted in the documentation [3]:
> >
> > - HTTP via Jolokia. See the documentation [4] for more details.
> > - Management messages. See the documentation [5] and the "management"
> > example for more details.
> >
> >
> > Justin
> >
> > [1] https://issues.apache.org/jira/browse/ARTEMIS-4409
> > [2]
> >
> >
> https://activemq.apache.org/components/artemis/documentation/latest/management.html#remote-jmx-access
> > [3]
> >
> >
> https://activemq.apache.org/components/artemis/documentation/latest/management.html
> > [4]
> >
> >
> https://activemq.apache.org/components/artemis/documentation/latest/management.html#exposing-jmx-using-jolokia
> > [5]
> >
> >
> https://activemq.apache.org/components/artemis/documentation/latest/management.html#using-management-message-api
> >
> > On Wed, Aug 30, 2023 at 10:07 AM Sargrad, Dave <dave.sarg...@saabinc.com
> >
> > wrote:
> >
> > >
> > > Hi.
> > > I've got an artemis broker running. I am able to browse to the admin
> > > portal at 8161. I also am able to publish and subscribe to 61616.
> > >
> > > I want to control the broker programmatically.
> > >
> > > I've searched for sample code to do this.
> > >
> > > All I've found seems to be this JMX enabled sample.
> > >
> > >
> > > https://github.com/apache/activemq-artemis/tree/main/examples/features
> > > /standard/client-kickoff
> > >
> > > Can someone point me to a sample that does not use JMX? Is JMX the
> > > only way to control an artemis broker programmatically?
> > >
> > > Assuming that the Broker always uses JMX for this type of programmatic
> > > control, do I need to configure this by adding the following
> > > attributes to the brokers JVM state?
> > > -Dcom.sun.management.jmxremote
> > > -Dcom.sun.management.jmxremote.port=3000
> > > -Dcom.sun.management.jmxremote.ssl=false
> > > -Dcom.sun.management.jmxremote.authenticate=false
> > >
> > > Thanks in advance for your guidance.
> > >
> > >
> > >
> > >
> > > This message is marked Public.
> > > This e-mail (including attachments) contains contents owned by Saab
> > > Group AB and/or its subsidiaries, affiliated companies or customers
> > > and covered by the laws of Sweden, the US, or Canada (federal, state or
> > provincial).
> > > The information is intended to be confidential and may be legally
> > > privileged. If you are not the intended recipient, you are hereby
> > > notified that any retention, dissemination, distribution, interception
> > > or copying of this communication is strictly prohibited and may
> > > subject you to further legal action. Reply to the sender if you
> > > received this email by accident, and then delete the email and any
> > attachments.
> > >
> > >
> > This e-mail (including attachments) contains contents owned by Saab Group
> > AB and/or its subsidiaries, affiliated companies or customers and covered
> > by the laws of Sweden, the US, or Canada (federal, state or provincial).
> > The information is intended to be confidential and may be legally
> > privileged. If you are not the intended recipient, you are hereby
> notified
> > that any retention, dissemination, distribution, interception or copying
> of
> > this communication is strictly prohibited and may subject you to further
> > legal action. Reply to the sender if you received this email by accident,
> > and then delete the email and any attachments.
> >
>
--
Clebert Suconic
