Learn how to create, use, and cache HTTP session data for your application.
On the internet, a web server doesn’t know who you are or what you do because it’s processing stateless HTTP requests. An HTTP session provides a way to store information to be used across multiple requests. Session variables store user information like user name or items in a shopping cart. By default, session variables will timeout after 30 minutes of being unused. Cookies, which also store user information, are maintained on a client’s computer, whereas session variables are maintained on a web server. For security reasons, an HTTP session is preferred over cookies when used with sensitive data. A session hides data from users. Cookies can be manipulated by a savvy user to make fake requests to your site.
High traffic websites must support thousands of users in a fast and reliable way. Load balancing requires running several instances of the same application in parallel so that traffic can be routed to different instances to maximize speed and reliability. Unless a user is tied to a particular instance, running multiple instances of the same application can pose an out-of-sync problem when each instance keeps an isolated copy of its session data. HTTP session data caching can solve this problem by allowing all instances of the application to share caches among each other. Sharing caches among instances eliminates the need to route a user to the same instance and helps in failover situations by distributing the cache.
You will learn how to build an application that creates and uses HTTP session data.
You will also learn how to use Open Liberty’s sessionCache feature to persist HTTP sessions
by using Java Caching (JCache), the standard caching API for Java.
You will containerize and deploy the application to a local Kubernetes cluster. You will then replicate the application in multiple pods and see that the session data is cached and shared among all instances of the application. Even if an instance is unavailable, the other instances are able to take over and handle requests from the same user by using the cached session data.
The application that you are working with is a shopping cart web service that uses JAX-RS,
which is a Java API for building RESTful web services.
You’ll learn how to persist a user’s shopping cart data between servers by using the
sessionCache feature in Open Liberty. The sessionCache feature persists HTTP
sessions using JCache. You can have high-performance HTTP session persistence
without using a relational database.
Navigate to the start directory to begin.
Create theCartApplicationclass.src/main/java/io/openliberty/guides/cart/CartApplication.java
CartApplication.java
link:finish/src/main/java/io/openliberty/guides/cart/CartApplication.java[role=include]The CartApplication class extends the generic JAX-RS application class that is needed to run the
application.
Create theCartResourceclass.src/main/java/io/openliberty/guides/cart/CartResource.java
CartResource.java
link:finish/src/main/java/io/openliberty/guides/cart/CartResource.java[role=include]The CartResource class defines the REST endpoints at which a user can make
an HTTP request.
The addToCart and getCart methods
have a number of annotations. Most of these annotations are used by the
MicroProfile OpenAPI and JAX-RS features to document the REST endpoints and map Java objects to web resources.
More information about these annotations can be found in the
Documenting RESTful APIs
and
Creating a RESTful web service
guides.
The cart/{item}&{price} endpoint demonstrates how to set session data.
The @PathParam annotation injects a custom item and
price from the POST request into the method parameter.
The addToCart method gets the current session and binds
the {item}:{price} key-value pair into the session by the setAttribute() method.
A response is then built and returned to confirm that an item was added to your cart and session.
The cart endpoint demonstrates how to get session data.
The getCart method gets the current session, iterates through all key-value
pairs that are stored in the current session, and creates a JsonObject response.
The JsonObject response is returned to confirm the server instance by
pod-name, the session by session-id,
and the items in your cart by cart.
Session caching is only valuable when a server is connected to at least one other member. There are two different ways session caching can behave in a cluster environment:
-
Client-server model: A Liberty server can act as the JCache client and connect to a dedicated JCache server.
-
Peer-to-peer model: A Liberty server can connect with other Liberty servers that are also running with the session cache and configured to be part of the same cluster.
You’ll use the peer-to-peer model in a Kubernetes environment for this guide.
JCache, which stands for Java Caching, is an interface
to standardize distributed caching on the Java platform.
The sessionCache feature uses JCache, which allows for session
persistence by providing a common cache of session data between servers.
This feature doesn’t include a JCache implementation.
For this guide, you’ll use Hazelcast as an open source JCache provider.
Hazelcast is a JCache provider. Open Liberty needs to be configured to use
Hazelcast after the sessionCache feature is enabled.
Create theserver.xmlfile.src/main/liberty/config/server.xml
server.xml
link:finish/src/main/liberty/config/server.xml[role=include]pom.xml
link:finish/pom.xml[role=include]The library element includes the library reference that indicates
to the server where the Hazelcast implementation of JCache is located.
Your Hazelcast implementation of JCache is a JAR file that resides in the shared resources directory that is defined by the file element.
The hazelcast-*.jar file is downloaded by the Liberty Maven plugin. The configuration is defined in the provided Maven POM file.
server.xml
link:finish/src/main/liberty/config/server.xml[role=include]By default, all Open Liberty servers that run the sessionCache
feature and Hazelcast are connected using a peer-to-peer model.
You can share the session cache only among certain Hazelcast instances
by using the cluster-name configuration element in the Hazelcast configuration file.
Create thehazelcast-config.xmlconfiguration file.src/main/liberty/config/hazelcast-config.xml
hazelcast-config.xml
link:finish/src/main/liberty/config/hazelcast-config.xml[role=include]The cluster name CartCluster is defined in the hazelcast-config.xml.
In the server.xml file, a reference to the Hazelcast configuration file is made by using
the httpSessionCache tag.
Create thebootstrap.propertiesfile.src/main/liberty/config/bootstrap.properties
bootstrap.properties
link:finish/src/main/liberty/config/bootstrap.properties[role=include]Hazelcast JCache provides the client and member providers. Set hazelcast.jcache.provider.type to member to use the member provider.
There are more configuration settings that you can explore in the Hazelcast documentation.
Point your browser to the http://localhost:9080/openapi/ui/ URL. This URL displays the available REST endpoints.
First, make a POST request to the /cart/{item}&{price} endpoint. To make this request, expand the POST
endpoint on the UI, click the Try it out button, provide an item and a price,
and then click the Execute button.
The POST request adds a user-specified item and price to a session
that represents data in a user’s cart.
Next, make a GET request to the /cart endpoint. To make this request, expand the GET
endpoint on the UI, click the Try it out button,
and then click the Execute button. The GET request
returns a pod name, a session ID, and all the items from your session.
Before you can deploy the application to Kubernetes, you need to containerize it with Docker.
Make sure to start your Docker daemon before you proceed.
The Dockerfile is provided at the start directory. If you’re unfamiliar with Dockerfile,
check out the Containerizing microservices guide,
which covers Dockerfile in depth.
Run the mvn package command from the start directory so that the .war file resides in the target directory.
mvn packageTo build and containerize the application, run the following Docker build command in the start directory:
docker build -t cart-app:1.0-SNAPSHOT .When the build finishes, run the following command to list all local Docker images:
docker imagesVerify that the cart-app:1.0-SNAPSHOT image is listed among the Docker images, for example:
REPOSITORY TAG
cart-app 1.0-SNAPSHOT
openliberty/open-liberty full-java11-openj9-ubikubernetes.yaml
link:finish/kubernetes.yaml[role=include]Now that the containerized application is built, deploy it to a local Kubernetes cluster by using
a Kubernetes resource definition, which is provided in the kubernetes.yaml file
at the start directory.
First, use the ClusterRoleBinding Kubernetes API object to grant Hazelcast members to access the cluster.
kubectl apply -f https://raw.githubusercontent.com/hazelcast/hazelcast/master/kubernetes-rbac.yamlRun the following command to deploy the application into 3 replicated pods as defined
in the kubernetes.yaml file:
kubectl apply -f kubernetes.yamlWhen the application is deployed, run the following command to check the status of your pods:
kubectl get podsYou see an output similar to the following if all the pods are working correctly:
NAME READY STATUS RESTARTS AGE cart-deployment-98f4ff789-2xlhs 1/1 Running 0 17s cart-deployment-98f4ff789-6rvfj 1/1 Running 0 17s cart-deployment-98f4ff789-qrh45 1/1 Running 0 17s
Point your browser to the http://localhost:31000/openapi/ui/ URL. This URL displays the available REST endpoints.
Run the minikube ip command to get the hostname for minikube.
Then, go to the http://[hostname]:31000/openapi/ui/ URL in your browser.
This URL displays the available REST endpoints.
Make a POST request to the /cart/{item}&{price} endpoint. To make this request, expand the POST
endpoint on the UI, click the Try it out button, provide an item and a price,
and then click the Execute button.
The POST request adds a user-specified item and price to a session
that represents data in a user’s cart.
Next, make a GET request to the /cart endpoint. To make this request, expand the GET
endpoint on the UI, click the Try it out button, and then click the Execute button.
The GET request returns a pod name, a session ID, and all the items from your session.
{
"pod-name": "cart-deployment-98f4ff789-2xlhs",
"session-id": "RyJKzmka6Yc-ZCMzEA8-uPq",
"cart": [
"eggs | $2.89"
],
"subtotal": 2.89
}
Replace the [pod-name] in the following command, and then run the command to pause
the pod for the GET request that you just ran:
kubectl exec -it [pod-name] -- /opt/ol/wlp/bin/server pauseRepeat the GET request. You see the same session-id
but a different pod-name because the session data is cached but the request
is served by a different pod (server).
Verify that the Hazelcast cluster is running by checking the Open Liberty log. To check the log, run the following command:
kubectl exec -it [pod-name] -- cat /logs/messages.logYou see a message similar to the following:
... [10.1.0.46]:5701 [CartCluster] [3.11.2]
Members {size:3, ver:3} [
Member [10.1.0.40]:5701 - 01227d80-501e-4789-ae9d-6fb348d794ea
Member [10.1.0.41]:5701 - a68d0ed1-f50e-4a4c-82b0-389f356b8c73 this
Member [10.1.0.42]:5701 - b0dfa05a-c110-45ed-9424-adb1b2896a3d
]
You can resume the paused pod by running the following command:
kubectl exec -it [pod-name] -- /opt/ol/wlp/bin/server resumeWhen you no longer need your deployed application, you can delete all Kubernetes resources and disable the Hazelcast members' access to the cluster by running the kubectl delete commands:
kubectl delete -f kubernetes.yaml
kubectl delete -f https://raw.githubusercontent.com/hazelcast/hazelcast/master/kubernetes-rbac.yamlYou have created, used, and cached HTTP session data for an application that was running on Open Liberty server and deployed in a Kubernetes cluster.