Problem with jboss-cli.sh in Wildfly 23 Final

[Chris Corless]

First of, I've started using the new WIldfly 23, and am very impressed, especially by the performance.

But there appears to be a minor regression between the Beta1 and Final versions.  The jboss-cli.sh script isn't working for me in the Final version.  It gives me a

 'jboss-cli.sh: 89: Syntax error: "(" unexpected'.  

and in the bash trace:

  jboss-cli.sh: line 59: setDefaultModularJvmOptions: command not found

This is on Linux.

However, it was easy to fix.  I copied over the jboss-cli.sh script from the Beta1 version, and it works fine.

[Jean Francois Denise]

Hi,

what is your sh (sh --version)? That should work calling "bash bin/jboss-cli.sh".

We have introduced syntax in jboss-cli.sh that is not supported when using sh. That explain the '(' unexpected.

I can't understand the "setDefaultModularJvmOptions" issue. It is not a new change, it is there since years.

JF

--
You received this message because you are subscribed to the Google Groups "WildFly" group.
To unsubscribe from this group and stop receiving emails from it, send an email to wildfly+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/wildfly/4fc98197-ba5a-4cac-948e-b9d37229d7dbn%40googlegroups.com.

[Chris Corless]

My mistake.  I wasn't running the script with bash before it.  

I was running it:

  jboss-cli.sh

If I run the script like this:

  bash jboss-cli.sh

it works without any errors.  In the past, I didn't need to run with the bash command, hence my confusion.

[Wolfgang Mayer]

Another approach ist to change the 1st line in jboss-cli.sh to

#!/bin/bash

[frank.l...@outlook.de]

There are already some open tickets targeting this problem. e.g.

- https://issues.redhat.com/browse/WFCORE-5315

- https://issues.redhat.com/browse/WFCORE-5333