[XPaaS] AMQ - Error after setting NO_PROXY with more than one server

Issue

• When updating from jboss-amq-6/amq63-openshift:1.3 to 1.4 the amq broker containers refuse to start when a no_proxy environment variable with more than 1 server is set e.g. "no_proxy=localhost,127.0.0.1".

• Editing the environment variables NO_PROXY to (for example) "a,b" (without the double-quotes) results with the pod doesn't start with the following output:

INFO Running jboss-amq-6/amq63-openshift image, version 1.4
Attempting to obtain lock for directory: (/opt/amq/data/split-1)
Successfully locked directory: (/opt/amq/data/split-1)
INFO: Loading '/opt/amq/bin/env'
INFO: Using java '/usr/lib/jvm/java-1.8.0/bin/java'
INFO: Starting in foreground, this is just for debugging purposes (stop process by pressing CTRL+C)
;: b: command not found
Usage: java [-options] class [args...]
           (to execute a class)
 ...