Missing Windows cmd files in 2.39.0 broker instance

[John Lilley <jo...@redpointglobal.com>]

Greetings,

It seems that in 2.39, making an instance on Windows doesn't create the instance\bin\artemis.cmd file that we got under 2.30.  We can work around this using Cygwin, and we don't use Windows in production, but was it removed intentionally?  Did I do something wrong creating the instance?  This is how we create it:

.\artemis create dmxbrokewr --user admin --password admin --silent --allow-anonymous --http-host

The root bin does have the artemis.cmd, just not the instance bin.  Can I just copy that to the instance?

Thanks
John

PLEASE NOTE: This e-mail from Redpoint Global Inc. ("Redpoint") is confidential and is intended solely for the use of the individual(s) to whom it is addressed. If you believe you received this e-mail in error, please notify the sender immediately, delete the e-mail from your computer and do not copy, print or disclose it to anyone else. If you properly received this e-mail as a customer, partner or vendor of Redpoint, you should maintain its contents in confidence subject to the terms and conditions of your agreement(s) with Redpoint.

Re: Missing Windows cmd files in 2.39.0 broker instance

[Robbie Gemmell <ro...@gmail.com>]

I think the answer might be in the original description that they "can
work around this using Cygwin". Was the instance perhaps also
*initially created* using Cygwin or such to begin with?

That will be detected and so be treated as creation for a *nix
instance, i.e not outputting .cmd files etc. The default create
behaviour is for the output created to match the env the create
command is being run in.

You can force what env output is created for by using flags on the
create command, e.g "--windows" and "--linux"

On Fri, 7 Mar 2025 at 22:21, Justin Bertram <jb...@apache.org> wrote:
>
> I just created a Windows 10 VM, installed OpenJDK 17, downloaded ActiveMQ
> Artemis 2.39.0 [1], unzipped it, and created an instance using the same
> command you used (except I had to specify a value for --http-host). The
> instance's "bin" directory contained "artemis.cmd" and I was able to use it
> to run the broker. Everything is working as expected.
>
> Can you provide me with step-by-step instructions to reproduce what you're
> seeing?
>
>
> Justin
>
> [1]
> https://www.apache.org/dyn/closer.cgi?filename=activemq/activemq-artemis/2.39.0/apache-artemis-2.39.0-bin.zip&action=download
>
> On Fri, Mar 7, 2025 at 1:57 PM John Lilley <jo...@redpointglobal.com>
> wrote:
>
> > Greetings,
> >
> > It seems that in 2.39, making an instance on Windows doesn't create the
> > instance\bin\artemis.cmd file that we got under 2.30.  We can work around
> > this using Cygwin, and we don't use Windows in production, but was it
> > removed intentionally?  Did I do something wrong creating the instance?
> > This is how we create it:
> >
> > .\artemis create dmxbrokewr --user admin --password admin --silent
> > --allow-anonymous --http-host
> >
> > The root bin does have the artemis.cmd, just not the instance bin.  Can I
> > just copy that to the instance?
> >
> > Thanks
> > John
> >
> > PLEASE NOTE: This e-mail from Redpoint Global Inc. ("Redpoint") is
> > confidential and is intended solely for the use of the individual(s) to
> > whom it is addressed. If you believe you received this e-mail in error,
> > please notify the sender immediately, delete the e-mail from your computer
> > and do not copy, print or disclose it to anyone else. If you properly
> > received this e-mail as a customer, partner or vendor of Redpoint, you
> > should maintain its contents in confidence subject to the terms and
> > conditions of your agreement(s) with Redpoint.
> >

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@activemq.apache.org
For additional commands, e-mail: users-help@activemq.apache.org
For further information, visit: https://activemq.apache.org/contact

Re: Missing Windows cmd files in 2.39.0 broker instance

[Justin Bertram <jb...@apache.org>]

I just created a Windows 10 VM, installed OpenJDK 17, downloaded ActiveMQ
Artemis 2.39.0 [1], unzipped it, and created an instance using the same
command you used (except I had to specify a value for --http-host). The
instance's "bin" directory contained "artemis.cmd" and I was able to use it
to run the broker. Everything is working as expected.

Can you provide me with step-by-step instructions to reproduce what you're
seeing?


Justin

[1]
https://www.apache.org/dyn/closer.cgi?filename=activemq/activemq-artemis/2.39.0/apache-artemis-2.39.0-bin.zip&action=download

On Fri, Mar 7, 2025 at 1:57 PM John Lilley <jo...@redpointglobal.com>
wrote:

> Greetings,
>
> It seems that in 2.39, making an instance on Windows doesn't create the
> instance\bin\artemis.cmd file that we got under 2.30.  We can work around
> this using Cygwin, and we don't use Windows in production, but was it
> removed intentionally?  Did I do something wrong creating the instance?
> This is how we create it:
>
> .\artemis create dmxbrokewr --user admin --password admin --silent
> --allow-anonymous --http-host
>
> The root bin does have the artemis.cmd, just not the instance bin.  Can I
> just copy that to the instance?
>
> Thanks
> John
>
> PLEASE NOTE: This e-mail from Redpoint Global Inc. ("Redpoint") is
> confidential and is intended solely for the use of the individual(s) to
> whom it is addressed. If you believe you received this e-mail in error,
> please notify the sender immediately, delete the e-mail from your computer
> and do not copy, print or disclose it to anyone else. If you properly
> received this e-mail as a customer, partner or vendor of Redpoint, you
> should maintain its contents in confidence subject to the terms and
> conditions of your agreement(s) with Redpoint.
>