1 Reply Latest reply on Jun 17, 2004 2:44 AM by Niklas Nobel

    session NOT sticky when switching from http to https

    Niklas Nobel Newbie

      using jboss-3.2.3, apache2(without ssl) and mod_jk2 on rh73.

      i have a copy of the all instance, called jboss0 on the same host as i run apache/mod-jk2 on and another instance called jboss1 on another host. both jvmRoute set in jboss-service.xml for tomcat. if the jboss0 host is targetted then the webapp works fine. but if the request is roundrobined to the jboss1 host i can see, in the accesslog for tomcat, a GET for index.jsp being redirected to my FORM-based authentication jsp page. next thing happening is a connectionrefused to the "jboss0 host":"https port of the jboss1 host". i understand the connection refused, wrong combination of host and https port, but why was the request redirected to the other host. seems the session is somehow sticky as the correct https port is used but the host is incorrect...

      would it make sense to build apache with ssl support? dont think it makes sense, the ajp13 protocol should be used nevertheless?

      if i run apache and both jboss instances on the same host everything works fine.

      cheers niklas.

        • 1. Re: session NOT sticky when switching from http to https
          Niklas Nobel Newbie

          if apache deals with ssl and both the http connector as well as the https connector is commented in jboss-service for the embedded tomcat then loadbalancing/failover using apache2/mod_jk2 works fine. i guess having tomcat dealing with https request whilst not dealing with http request would leave the loadbalancer out of the ballgame with respect to https request. if you could configure such a solution then you would have a https single point of failure.

          cheers niklas.