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

Solution Verified - Updated -

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)
 ...

Environment

  • Red Hat AMQ : 6.3.0
  • OpenShift : 3.x
  • Image : jboss-amq-6/amq63-openshift:1.4

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.