Uploaded image for project: 'Cloud Enablement'
  1. Cloud Enablement
  2. CLOUD-2821

Continuing problems with NO_PROXY in Java pods

    XMLWordPrintable

Details

    • Hide

      1. Create an A-MQ 6.3 deployment on OpenShift (MiniShift will do) as described in our documentation
      2. Edit (if necessary) the DC to ensure that image version amq63-openshift:1.4 is used
      3. Ensure broker pod starts
      4. Edit the environment variables to set NO_PROXY to (for example) "a,b" (without the double-quotes)
      5. Note that the pod will not start up. Error message is

      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)
 ...
      Show
      1. Create an A-MQ 6.3 deployment on OpenShift (MiniShift will do) as described in our documentation 2. Edit (if necessary) the DC to ensure that image version amq63-openshift:1.4 is used 3. Ensure broker pod starts 4. Edit the environment variables to set NO_PROXY to (for example) "a,b" (without the double-quotes) 5. Note that the pod will not start up. Error message is 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) ...
    • CLOUD Maintenance Sprint 25

    Description

      There have been problems in the past with the way that the A-MQ image (or, rather, the underlying Java image) handles the conversion of the Docker environment variable NO_PROXY. This is usually specified in the form "host1,host2..." separate by commas, and this needs to be translated into

      -Dhttp.nonProxyHosts="host1|host2|..."

      on the JVM command line. The translation takes place in the script /opt/run-java/proxy-options. Despite recent changes (e.g., CLOUD-1951) the translation is still wrong. What actually gets written is

      -Dhttp.nonProxyHosts=host1|host2|...

      so the shell interprets |host2 as a pipe, and tries to execute host2.

      Attachments

        Issue Links

          is related to

          Bug - A problem that impairs or prevents the functions of the product. CLOUD-2747 [JWS][Regression] JWS container fails to start if NO_PROXY env is set

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Verified

          Activity

            People

              gaohoward Howard Gao
              rhn-support-kboone Kevin Boone
              Petr Nehyba Petr Nehyba (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: