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

Java console link fails for A-MQ based pod with TLS handshake timeout error

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: AMQ62 1.3.5.GA
    • Fix Version/s: None
    • Component/s: AMQ
    • Labels:
      None
    • Steps to Reproduce:
      Hide
      1. Create a project
      2. Follow the documented steps for creating an AMQ pod
      3. Browse to the Openshift web console and navigate to the newly deployed AMQ pods detail page and click on the "Open Java Console" link

      Curl can also be used to test the connection to the Jolokia agent. The following example assumes the terminal user has already logged onto an Opesnhift environment using 'oc login...'. Replace the following placeholders in the curl url with appropriate values for your OCP environment: OCP-MASTER-URL, AMQ-PROJECT, AMQ-POD-NAME

      export token=`oc whoami -t`
      curl -v https://OCP-MASTER-URL/api/v1/namespaces/AMQ-PROJECT/pods/https:AMQ-POD-NAME:8778/proxy/jolokia/version -H "Authorization: Bearer $token" --insecure
      
      Show
      Create a project Follow the documented steps for creating an AMQ pod Browse to the Openshift web console and navigate to the newly deployed AMQ pods detail page and click on the "Open Java Console" link Curl can also be used to test the connection to the Jolokia agent. The following example assumes the terminal user has already logged onto an Opesnhift environment using 'oc login...'. Replace the following placeholders in the curl url with appropriate values for your OCP environment: OCP-MASTER-URL, AMQ-PROJECT, AMQ-POD-NAME export token=`oc whoami -t` curl -v https://OCP-MASTER-URL/api/v1/namespaces/AMQ-PROJECT/pods/https:AMQ-POD-NAME:8778/proxy/jolokia/version -H "Authorization: Bearer $token" --insecure
    • Affects:
      User Experience
    • Bugzilla Update:
      Perform

      Description

      After creating an AMQ based pod using an xPaaS provided template, clicking on the Open Java Console link from the Pod details screen of the Openshift web console fails with a TLS handshake timeout error.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  kconner Kevin Conner
                  Reporter:
                  trogers-rh Travis Rogers
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  3 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: