3 Replies Latest reply on Aug 18, 2016 12:11 PM by Justin Bertram

    Running jboss-eap-quickstarts-7.0.0.GA\helloworld-jms through proxy.

    James Hayes Newbie

      Using EAP7 and running the jboss-eap-quickstarts-7.0.0.GA\helloworld-jms example results in successful communication to the local EAP server and remote EAP server.

       

      Using the -Dhttp.proxyHost=10.1.0.149 -Dhttp.proxyPort=3128 command line options when invoking the client program is expected to send messages through the proxy server at 10.1.0.149:3128 however continues to use the address encoded in the PROVIDER_URL.

        • 1. Re: Running jboss-eap-quickstarts-7.0.0.GA\helloworld-jms through proxy.
          Justin Bertram Master

          Does any traffic at all go through the proxy?  If so, at what point does it stop?

           

          One thing to keep in mind here is that the helloworld-jms quickstart uses both JNDI and JMS connections and each are implemented independently of each other.  The JNDI lookup gets the connection factory stub from the server and then the JMS implementation uses that to make its connection.  The JMS connection starts out as HTTP but then "upgrades" (via the HTTP upgrade header) to a non-HTTP connection at which point I wouldn't expect the proxy to be involved anymore.

          • 2. Re: Running jboss-eap-quickstarts-7.0.0.GA\helloworld-jms through proxy.
            James Hayes Newbie

            Currently using default example (jboss-eap-quickstarts-7.0.0.GA\helloworld-jms) but just setting PROVIDER_URL to remote address, no traffic goes through the proxy when java is invoked with httpProxy argument; no connections are made. Can JNDI and JMS be configured to always use HTTP and proxy?

             

            There is expectation by how the browser works on Windows when the system level proxy server is set from the "Internet Properties->Local Area Network (LAN) Settings->Proxy server", all browsers go to the proxy no matter type i.e. either Chrome or IE.

            • 3. Re: Running jboss-eap-quickstarts-7.0.0.GA\helloworld-jms through proxy.
              Justin Bertram Master

              I can't address your question related to JNDI since I don't know much about the implementation, but I can say that I don't think it's possible to route JMS traffic through an HTTP proxy because JMS doesn't use HTTP except for a very short time at the beginning of the connection (and that's true only when it's configured to use an http-connector).

               

              What you say about Chrome and IE makes sense because they both use HTTP.  But as I already indicated JMS doesn't work that way.