Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-5860

The websocket-client quickstart fails to connect to secured backend in DR3

    XMLWordPrintable

Details

    • Bug
    • Status: Verified (View Workflow)
    • Critical
    • Resolution: Done
    • 7.1.0.DR3
    • 7.1.0.DR5
    • Web Sockets
    • None

    Description

      There has been a change in behavior between the JBoss EAP server 7.1 DR2 and 7.1 DR3 builds.

      The websocket-client quickstart uses a relay between a frontend WebSocket server endpoint and a backend WebSocket client endpoint. It connects to a publicly available echo server using a secured connection: wss://echo.websocket.org

      I have tested this quickstart [1] against JBoss EAP 7.0 GA, 7.1 DR, and 7.1 DR2 and it works as expected.

      When I test it using the JBoss EAP server DR3 build, I get this error:

      Failed to connect to backend wss://echo.websocket.org: Invalid response code 404
      

      I also tested it against a build of the current source (7.x) for JBoss EAP 7, and it fails with the same message.

      Something changed between DR2 and DR3 that results in the failure of this quickstart.

      [1] https://github.com/jboss-developer/jboss-eap-quickstarts/tree/7.1.x-develop/websocket-client

      Attachments

        Issue Links

          Activity

            People

              sdouglas1@redhat.com Stuart Douglas
              sgilda_jira Sande Gilda (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: