Apache2 ws_tunnel and many Tomcat instances












0















I have working 2 Tomcat running instances.


1) working on HTTP :8080/app1 and HTTPS :8443/app1 WS endpoint /app1/websocket

2) working on HTTP :8081/app2 and HTTPS :8444/app2 WS endpoint /app2/websocket



I have prepared site configuration for domain.conf



<VirtualHost *:443>
ServerName domain
ServerAdmin webmaster@localhost
DocumentRoot /var/www/html
ErrorLog ${APACHE_LOG_DIR}/domain_error.log
CustomLog ${APACHE_LOG_DIR}/domain_access.log combined
SSLCertificateFile /etc/letsencrypt/live/domain-0002/fullchain.pem
SSLCertificateKeyFile /etc/letsencrypt/live/domain-0002/privkey.pem
<Location "/app2/websocket">
ProxyPass "ws://127.0.0.1:8081/app2/websocket"
ProxyPassReverse "ws://127.0.0.1:8081/app2/websocket"
</Location>

<Location "/app2">
ProxyPass "http://127.0.0.1:8081/app2"
ProxyPassReverse "http://127.0.0.1:8081/app2"
</Location>

<Location "/app1">
ProxyPass "http://127.0.0.1:8080/app1"
ProxyPassReverse "http://127.0.0.1:8080/app1"
</Location>

<Location "/app1/websocket">
ProxyPass "ws://127.0.0.1:8080/app1/websocket"
ProxyPassReverse "ws://127.0.0.1:8080/app1/websocket"
</Location>


The problem is with my mobile app.
When I connect to app1 websocket works perfectly but after I connect to app2 websocket isn't connected. In apache log I see 500 for app1 (WS Works) and 404 for app2 (WS doesn't work)










share|improve this question



























    0















    I have working 2 Tomcat running instances.


    1) working on HTTP :8080/app1 and HTTPS :8443/app1 WS endpoint /app1/websocket

    2) working on HTTP :8081/app2 and HTTPS :8444/app2 WS endpoint /app2/websocket



    I have prepared site configuration for domain.conf



    <VirtualHost *:443>
    ServerName domain
    ServerAdmin webmaster@localhost
    DocumentRoot /var/www/html
    ErrorLog ${APACHE_LOG_DIR}/domain_error.log
    CustomLog ${APACHE_LOG_DIR}/domain_access.log combined
    SSLCertificateFile /etc/letsencrypt/live/domain-0002/fullchain.pem
    SSLCertificateKeyFile /etc/letsencrypt/live/domain-0002/privkey.pem
    <Location "/app2/websocket">
    ProxyPass "ws://127.0.0.1:8081/app2/websocket"
    ProxyPassReverse "ws://127.0.0.1:8081/app2/websocket"
    </Location>

    <Location "/app2">
    ProxyPass "http://127.0.0.1:8081/app2"
    ProxyPassReverse "http://127.0.0.1:8081/app2"
    </Location>

    <Location "/app1">
    ProxyPass "http://127.0.0.1:8080/app1"
    ProxyPassReverse "http://127.0.0.1:8080/app1"
    </Location>

    <Location "/app1/websocket">
    ProxyPass "ws://127.0.0.1:8080/app1/websocket"
    ProxyPassReverse "ws://127.0.0.1:8080/app1/websocket"
    </Location>


    The problem is with my mobile app.
    When I connect to app1 websocket works perfectly but after I connect to app2 websocket isn't connected. In apache log I see 500 for app1 (WS Works) and 404 for app2 (WS doesn't work)










    share|improve this question

























      0












      0








      0








      I have working 2 Tomcat running instances.


      1) working on HTTP :8080/app1 and HTTPS :8443/app1 WS endpoint /app1/websocket

      2) working on HTTP :8081/app2 and HTTPS :8444/app2 WS endpoint /app2/websocket



      I have prepared site configuration for domain.conf



      <VirtualHost *:443>
      ServerName domain
      ServerAdmin webmaster@localhost
      DocumentRoot /var/www/html
      ErrorLog ${APACHE_LOG_DIR}/domain_error.log
      CustomLog ${APACHE_LOG_DIR}/domain_access.log combined
      SSLCertificateFile /etc/letsencrypt/live/domain-0002/fullchain.pem
      SSLCertificateKeyFile /etc/letsencrypt/live/domain-0002/privkey.pem
      <Location "/app2/websocket">
      ProxyPass "ws://127.0.0.1:8081/app2/websocket"
      ProxyPassReverse "ws://127.0.0.1:8081/app2/websocket"
      </Location>

      <Location "/app2">
      ProxyPass "http://127.0.0.1:8081/app2"
      ProxyPassReverse "http://127.0.0.1:8081/app2"
      </Location>

      <Location "/app1">
      ProxyPass "http://127.0.0.1:8080/app1"
      ProxyPassReverse "http://127.0.0.1:8080/app1"
      </Location>

      <Location "/app1/websocket">
      ProxyPass "ws://127.0.0.1:8080/app1/websocket"
      ProxyPassReverse "ws://127.0.0.1:8080/app1/websocket"
      </Location>


      The problem is with my mobile app.
      When I connect to app1 websocket works perfectly but after I connect to app2 websocket isn't connected. In apache log I see 500 for app1 (WS Works) and 404 for app2 (WS doesn't work)










      share|improve this question














      I have working 2 Tomcat running instances.


      1) working on HTTP :8080/app1 and HTTPS :8443/app1 WS endpoint /app1/websocket

      2) working on HTTP :8081/app2 and HTTPS :8444/app2 WS endpoint /app2/websocket



      I have prepared site configuration for domain.conf



      <VirtualHost *:443>
      ServerName domain
      ServerAdmin webmaster@localhost
      DocumentRoot /var/www/html
      ErrorLog ${APACHE_LOG_DIR}/domain_error.log
      CustomLog ${APACHE_LOG_DIR}/domain_access.log combined
      SSLCertificateFile /etc/letsencrypt/live/domain-0002/fullchain.pem
      SSLCertificateKeyFile /etc/letsencrypt/live/domain-0002/privkey.pem
      <Location "/app2/websocket">
      ProxyPass "ws://127.0.0.1:8081/app2/websocket"
      ProxyPassReverse "ws://127.0.0.1:8081/app2/websocket"
      </Location>

      <Location "/app2">
      ProxyPass "http://127.0.0.1:8081/app2"
      ProxyPassReverse "http://127.0.0.1:8081/app2"
      </Location>

      <Location "/app1">
      ProxyPass "http://127.0.0.1:8080/app1"
      ProxyPassReverse "http://127.0.0.1:8080/app1"
      </Location>

      <Location "/app1/websocket">
      ProxyPass "ws://127.0.0.1:8080/app1/websocket"
      ProxyPassReverse "ws://127.0.0.1:8080/app1/websocket"
      </Location>


      The problem is with my mobile app.
      When I connect to app1 websocket works perfectly but after I connect to app2 websocket isn't connected. In apache log I see 500 for app1 (WS Works) and 404 for app2 (WS doesn't work)







      apache-http-server tomcat






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Jan 16 at 16:14









      Marcin PiękośMarcin Piękoś

      11




      11






















          0






          active

          oldest

          votes











          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "3"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1395015%2fapache2-ws-tunnel-and-many-tomcat-instances%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          0






          active

          oldest

          votes








          0






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes
















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Super User!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1395015%2fapache2-ws-tunnel-and-many-tomcat-instances%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown