[ 
https://issues.apache.org/jira/browse/ARTEMIS-4504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17786283#comment-17786283
 ] 

ASF subversion and git services commented on ARTEMIS-4504:
----------------------------------------------------------

Commit 6f14de77be4b486e8da5e1f08e681fe3bc817485 in activemq-artemis's branch 
refs/heads/main from Robbie Gemmell
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=6f14de77be ]

ARTEMIS-4504: add a stop goal that runs the cli script, update examples to use 
it


> running examples creates unexpected dirs/files (or shows failure trying)
> ------------------------------------------------------------------------
>
>                 Key: ARTEMIS-4504
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-4504
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>    Affects Versions: 2.31.2
>            Reporter: Robbie Gemmell
>            Assignee: Robbie Gemmell
>            Priority: Minor
>             Fix For: 2.32.0
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Running one of the examples with e.g mvn verify will typically create and 
> leave behind an unexpected sub directory within the example source dir called 
> "${sys:artemis.instance}/log" with [empty] artemis.log and audit.log files 
> inside. Alternatively, on some systems it may instead fail while trying to do 
> this and display an error message about it.
> This happens because the plugin used by the examples first creates a broker 
> instance within the target directory, prompting creation of a related 
> log4j2.properties file, then at the end of the example the plugin is again 
> used to run the CLI stop command to shut down the broker, the process for 
> which currently runs the CLI class directly without some of the configuration 
> properties the CLI script normally sets, and in doing this puts the broker 
> instance log42.properties file on the classpath and then causes log4j to be 
> initialised which leads to the erroneous dir+file creation due to the missing 
> props. We can resolve this by updating the example/plugin to call the CLI 
> script such that the needed config is actually present.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to