1 Reply Latest reply on Jun 4, 2004 12:28 PM by Darryl Thompson

    Setting up cookies with Jetty, Jboss 3.2.3 and Apache/mod_jk

    jaffadan Newbie

      I asked this question in the cluster forum and did not get any response.

      I am having problems clustering 2 jboss 3.2.3 + jetty servers using Apache + mod_jk2.

      I have the two jboss server working correctly in the cluster. (Drop a ear in the farm directory and it is farmed out to my other server)

      It seems that i have Apache + mod_jk2 configured correctly since i can take down either server and i still can hit my main page.

      But my problem lies in that when i look at the generated cookie it seems to be jboss/jetty server specific. Ie
      a0r2b4mlao6mg.10.132.240.241:8009 and 1hlcjcubdihic.10.132.240.242:8009 . It seems as if the session is lost every page i hit as a new cookie is generated.

      Thank you for any help.

        • 1. Re: Setting up cookies with Jetty, Jboss 3.2.3 and Apache/mo
          Darryl Thompson Newbie

          Hello,

          I am having a problem getting to my clustered JBoss servers (each instance is running on a different machine) via Apache 2.0.49 using mod_jk2 maybe you can help me figure out what is wrong.

          To begin:

          1) I have clustered JBoss 3.2.4RC2 by creating another instance of the "all" server. I have changed cluster-service.xml to include "jvmRoute=jboss1".

          2) I have copied my new JBoss "all" to two different machines and when I start them they both are clustered; so that part works.


          3) I have installed Apache 2.0.49 on a 3rd machine and added the mod_jk2 connector to modules/mod_jk2 (here it seems that the suffix is .so and not .dll even though this is the win32 connector).

          4) in the httpd/conf/httpd file I added the following to the end of the script
          LoadModule jk2_module modules/mod_jk2.so

          5) I created the following workers2.properties file:

          [logger]
          level=DEBUG

          [config:]
          #file=/conf/workers2.properties
          file=C:/appServer/Apache/Apache2/conf/workers2.properties
          debug=5
          debugEnv=0

          [uriMap:]
          info=Maps the requests. Options: debug
          debug=0

          # Alternate file logger
          [logger.file:0]
          level=DEBUG
          file=C:/appServer/Apache/Apache2/logs/jk2.log

          [shm:]
          info=Scoreboard. Required for reconfiguration and status with multiprocess servers
          file=C:/appServer/Apache/Apache2/logs/jk2.shm
          size=10000
          debug=0
          disabled=0

          [workerEnv:]
          info=Global server options
          timing=1
          debug=0
          # Default Native Logger (apache2 or win32 )
          # can be overriden to a file logger, useful
          # when tracing win32 related issues
          #logger=logger.file:0

          # Loadbalancer
          [lb:lb]
          info=Default load balancer.
          debug=5
          stickySession=1

          # First Tomcat Instance
          [channel.socket:192.168.100.33:8109]
          info=Ajp13 forwarding over socket
          debug=5
          tomcatId=jboss1:8109
          port=8109
          host=192.168.100.33
          disabled=0

          [ajp13:192.168.100.33:8109]
          channel=channel.socket:192.168.100.33:8109
          group=lb
          lb_factor=1


          # Second Tomcat Instance
          [channel.socket:192.168.100.34:8109]
          info=Ajp13 forwarding over socket
          debug=5
          tomcatId=jboss2:8109
          port=8109
          host=192.168.100.34
          disabled=0

          [ajp13:192.168.100.34:8109]
          channel=channel.socket:192.168.100.34:8109
          group=lb
          lb_factor=1

          [status:]
          info=Status worker, displays runtime informations

          # Uri mapping
          [uri:/*.jsp]
          group=lb

          [uri:/jsf-guessNumber/*]
          group=lb

          [uri:/servlet/*]
          group=lb


          6) Restarted Apache2 service on WinXP machine
          7) on WinXP machine:
          enter http://localhost -- get default page OK
          enter http://localhost/jsf-guessNumber --get 404 page not found

          Note: jsf-guessNumber.war is installed on all servers in cluster.

          8) on winXP machine:
          enter http://192.168.100.33:8180/jsf-guessNumber/ -- page shows
          enter http://192.168.100.34:8180/jsf-guessNumber/ -- page shows



          Any idea why mod2 connector not going to JBoss???