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

[JWS] Application will not start with NO_PROXY settings

    XMLWordPrintable

Details

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

    Description

      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

      Attachments

        Issue Links

          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. CLOUD-1636 [SSO70] Application will not start with NO_PROXY settings

          • 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.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. CLOUD-1728 [JWS3.1] Application will not start with NO_PROXY settings

          • 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.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. CLOUD-1629 [AMQ] Application will not start with NO_PROXY settings

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. CLOUD-1630 [JDV] Application will not start with NO_PROXY settings

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. CLOUD-1631 [EAP64] Application will not start with NO_PROXY settings

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. CLOUD-1632 [EAP70] Application will not start with NO_PROXY settings

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. CLOUD-1633 [JAVA8] Application will not start with NO_PROXY settings

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. CLOUD-1634 [JDG] Application will not start with NO_PROXY settings

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. CLOUD-1635 [KIESERVER] Application will not start with NO_PROXY settings

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. CLOUD-1637 [SSO71] Application will not start with NO_PROXY settings

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: