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

[JWS] Application will not start with NO_PROXY settings

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Critical Critical
    • JWS30 1.3.0.GA
    • None
    • JWS3
    • None
    • CLOUD Maintenance Sprint 5

      CLOUD-865 brought support for http proxy setting in runtime. When NO_PROXY is set with wildcards the container will fail to start

      Tomcat 8

      Running jboss-webserver-3/webserver30-tomcat8-openshift image, version 1.3-2
/opt/webserver/bin/catalina.sh: line 362: 127.*: command not found
/opt/webserver/bin/catalina.sh: line 362: *.xpaas: command not found
Picked up JAVA_TOOL_OPTIONS: -Duser.home=/home/jboss -Duser.name=jboss
Usage: java [-options] class [args...]
           (to execute a class)
   or  java [-options] -jar jarfile [args...]
           (to execute a jar file)

      Tomcat 7

      Running jboss-webserver-3/webserver30-tomcat7-openshift image, version 1.3-2
/opt/webserver/bin/catalina.sh: line 348: 127.*: command not found
/opt/webserver/bin/catalina.sh: line 348: *.xpaas: command not found
Picked up JAVA_TOOL_OPTIONS: -Duser.home=/home/jboss -Duser.name=jboss
Usage: java [-options] class [args...]
           (to execute a class)
   or  java [-options] -jar jarfile [args...]
           (to execute a jar file)

      jpechane@jpechane:~/sources/xpaas-qe$ oc env pod app-2-2hhgq --list
# pods app-2-2hhgq, container app
http_proxy=http://proxy-new-service:3128/
no_proxy=10.*,127.*,*.xpaas

              kliberti Kyle Liberti
              jpechane Jiri Pechanec
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: