Austen, CEO und Dr. Ulf Martin, COO
>
> P Please check whether a printout of this e-mail is really necessary.
>
>
>
>
> Von: "Justin Bertram"
> An:users@activemq.apache.org
> Datum:02.01.2024 16:19
> Betreff:[Ext] Re: no-acceptor op
users@activemq.apache.org
Datum: 02.01.2024 16:19
Betreff:[Ext] Re: no-acceptor options not understood
The --no-*-acceptor parameters simply omit the specific acceptor for that
particular protocol. They are a simple way to reduce the number of ports
the broker is listening on.
For examp
?
>
> Best Regards
>
> Herbert
>
>
>
> Von:"Domenico Francesco Bruscino"
> An:users@activemq.apache.org
> Datum: 02.01.2024 15:51
> Betreff:[Ext] Re: no-acceptor options not understood
> --
>
&g
51
Betreff:[Ext] Re: no-acceptor options not understood
Hi Herbert,
there is no way to pass the list of the desired acceptor protocols to the
artemis create command.
You could use broker properties to overwrite it at runtime, i.e.
artemis create --ja
The --no-*-acceptor parameters simply omit the specific acceptor for that
particular protocol. They are a simple way to reduce the number of ports
the broker is listening on.
For example, if you specify --no-amqp-acceptor then the acceptor named
"amqp" listening on port 5672 will be omitted.
This
Hi Herbert,
there is no way to pass the list of the desired acceptor protocols to the
artemis create command.
You could use broker properties to overwrite it at runtime, i.e.
artemis create --java-options
'-DacceptorConfigurations.artemis.params.protocols=CORE,OPENWIRE'
Alternatively, you could
Hello Team,
when creating an instance ofaremis broker 2.21.2 in the broker create
script iI have defined
export ARGS="$ARGS --no-amqp-acceptor true"
export ARGS="$ARGS --no-hornetq-acceptor true"
export ARGS="$ARGS --no-mqtt-acceptor true"
export ARGS="$ARGS --no
