EAP 6.1.0 different jboss-cli behaviour with automated bash scripts

Solution Verified - Updated -

Issue

In JBoss EAP 6.0 user made a set of jboss-cli support scripts using bash (on Linux).
With JBoss EAP 6.1 these scripts are working no more.

Here is an example of a script which fails

#!/bin/bash
PROFILE=$1

jboss-cli.sh -c <<EOF
batch
/profile=$PROFILE/subsystem=remoting/connector=remoting-connector:write-attribute(name=security-realm,value=ManagementRealm)
/profile=$PROFILE/subsystem=jmx/remoting-connector=jmx:add(use-management-endpoint=false)
run-batch
EOF

It seems that with EAP 6.1 jboss-cli.sh the stdin stream is not correctly read from batch lines, so the shell script is blocking may be still waiting for input. Ctrl-C on console is the only way to stop it.

  • What happened to the jboss-cli.sh?
  • What's the difference between 6.0 and 6.1 jboss-cli?
  • How should we write batch scripts to make them compatible with ALL current and future versions of jboss-cli?

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP)
    • 6.1.0
  • Linux bash scripts

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content