OK, I had overlooked "script found under the bin directory of the
newly created broker" and looked only at the command line examples:
$ ./artemis create $directory
$ ./artemis run
It works now. Thanks very much for your help.
Am Mo., 28. Sept. 2020 um 14:28 Uhr schrieb Robbie Gemmell
:
>
> You
You did create one yes, however you then didn't actually go on to use
it, and instead tried issuing the run command to the base script
again, which doesnt support it as it then indicates.
Note the output during creation includes some example commands for
running the broker instance, which uses a
I dont know if there is already a simple a way to use Logback
directly/indirectly (without e.g implementing such a handler), but in
terms of log rotation I see from etc/logging.properties that the
config shows
handler.FILE=org.jboss.logmanager.handlers.PeriodicRotatingFileHandler
is the default
I think I created an instance. The complete journal:
C:\java\apache-artemis-2.15.0\bin>dir
Datenträger in Laufwerk C: ist Windows
Volumeseriennummer: F4C1-7A8D
Verzeichnis von C:\java\apache-artemis-2.15.0\bin
24.08.2020 20:45 .
24.08.2020 20:45 ..
24.08.2020
The below suggests you are trying to run the initial instal etc tool
script, rather than a broker instance script used to start a specific
broker. Did you create a broker instance as detailed in the readme
(see the create command listed in the help output below) ? That
creates a further script
Thanks to the AWS support team for looking into this problem. I will give it a
try.
Thanks a lot!
Fabrice
From: Tim Bain
Sent: 26 September 2020 15:26
To: ActiveMQ Users
Subject: Re: Please help me with authorisation configuration
CAUTION: This email
Hi,
I tried to run artemis as in the README.html
How should I start the broker?
C:\java\apache-artemis-2.15.0\bin>artemis.cmd run
Found unexpected parameters: [run]
usage: artemis []
The most commonly used artemis commands are:
address Address tools group (create|delete|update|show)
