Group Discounts available for 3+ students and Corporate Clients

Enabling Sticky Sessions – JBoss

Sticky Sessions in JBoss

In workers.properties update lb worker:

worker.jboss.sticky_session=1

On a UNIX system add to jk.conf:

JkShmFile logs/jk.shm

In each Tomcats’ server.xml set: <Engine … jvmRoute=”jboss1″> (or jboss2)

Interested in mastering JBOSS?
Learn more about JBOSS Tutorial in this blog post.

After restarting, test with two browsers

Directive sticky_session is set to 1 (or True) by default, but we turn it on to make it explicit.

Enabling the shared memory file (JkShmFile) is not required, but allows the HTTPD processes to better communicate on a prefork-type system.

The value of the jvmRoute attribute in server.xml`s `<Engine> must match the name of the worker instance as configured in the workers.properties file.

For indepth understanding on JBoss click on:

“At TekSlate, we are trying to create high quality tutorials and articles, if you think any information is incorrect or want to add anything to the article, please feel free to get in touch with us at info@tekslate.com, we will update the article in 24 hours.”

0 Responses on Enabling Sticky Sessions - JBoss"

    Leave a Message

    Your email address will not be published. Required fields are marked *

    Support


    Please Enter Your Details and Query.
    Three + 6