Session sharing in Apache Tomcat

本文介绍如何在Apache Tomcat 6中实现多个应用间的会话数据共享,包括配置空会话路径、允许跨上下文访问及使用跨上下文数据共享等步骤。
Sometimes when you want to create large portal-like application which consists of a few smaller applications, or you want to create your own SSO domain, you must share session and session data between all interested applications.

Today I will show you how you can share session and data across applications in Apache Tomcat 6.


Enabling session sharing

Open $CATALINA_HOME/conf/server.xml, find the 8080 connector definition:
view sourceprint?1.<Connector port="8080" protocol="HTTP/1.1" connectionTimeout="20000" redirectPort="8443" />and simply add emptySessionPath="true" attribute to it so that it looks something like this:
view sourceprint?1.<Connector port="8080" protocol="HTTP/1.1" emptySessionPath="true" connectionTimeout="20000" redirectPort="8443" />Test projects

I created two simple applications called session1 and session2.

session1 increments the counter:
view sourceprint?01.<%@ taglib uri="http://java.sun.com/jsp/jstl/core" prefix="c"%>
02.<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
03.<html>
04.<head>
05.<title>++</title>
06.</head>
07.<body>
08.<h1>I'm incrementing the counter!</h1>
09.<c:set var="counter" value="${sessionScope.counter + 1}" scope="session" />
10.<h1>Current counter value is ${sessionScope.counter}</h1>
11.</body>
12.</html>session2 decrements the counter:
view sourceprint?01.<%@ taglib uri="http://java.sun.com/jsp/jstl/core" prefix="c"%>
02.<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
03.<html>
04.<head>
05.<title>--</title>
06.</head>
07.<body>
08.<h1>I'm decrementing the counter!</h1>
09.<c:set var="counter" value="${sessionScope.counter - 1}" scope="session" />
10.<h1>Current counter value is ${sessionScope.counter}</h1>
11.</body>
12.</html>Deploying and testing

When I deployed both applications and refreshed a few times their index pages:
view sourceprint?1.http://localhost:8080/session1/
2.http://localhost:8080/session2/although the JSESSIONID cookie was the same:

counters were independent. The first one showed +4, the second one showed -4.

The problem and the solution

Problem: even though the session id is the same in both applications you cannot share data directly using HttpSession object.

Solution: you have to use session-aware cross contexts in order to share data between applications.

Cross contexts in Apache Tomcat

First you have to allow applications to access each others' contexts.

Open $CATALINA_HOME/conf/context.xml and add crossContext="true" attribute to the <Context /> root element:
view sourceprint?1.<?xml version='1.0' encoding='utf-8'?>
2.<Context crossContext="true">
3.<WatchedResource>WEB-INF/web.xml</WatchedResource>
4.<Manager pathname="" />
5.</Context>Re-start the server.

Cross context data sharing

Please note that I highly loath scriptlets, I only show them in order to simplify the listing :)

Edit index.jsp of the session1 application so that it looks like this:
view sourceprint?01.<%@ taglib uri="http://java.sun.com/jsp/jstl/core" prefix="c"%>
02.<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
03.<html>
04.<head>
05.<title>++</title>
06.</head>
07.<body>
08.<%
09.ServletContext siblingContext = request.getSession().getServletContext().getContext("/session1");
10.Integer counter = (Integer)siblingContext.getAttribute("counter");
11.if (counter == null) {
12.counter = 0;
13.}
14.counter++;
15.request.setAttribute("counter", counter);
16.siblingContext.setAttribute("counter", counter);
17.%>
18.<h1>I'm incrementing counter!</h1>
19.<h1>Current counter value is ${counter}!</h1>
20.</body>
21.</html>Then, modify the session2 application:
view sourceprint?01.<%@ taglib uri="http://java.sun.com/jsp/jstl/core" prefix="c"%>
02.<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
03.<html>
04.<head>
05.<title>--</title>
06.</head>
07.<body>
08.<%
09.ServletContext siblingContext = request.getSession().getServletContext().getContext("/session1");
10.Integer counter = (Integer)siblingContext.getAttribute("counter");
11.if (counter == null) {
12.counter = 0;
13.}
14.counter--;
15.request.setAttribute("counter", counter);
16.siblingContext.setAttribute("counter", counter);
17.%>
18.<h1>I'm decrementing counter!</h1>
19.<h1>Current counter value is ${counter}!</h1>
20.</body>
21.</html>Re-deploy both applications.

Now, when you access both applications, you will see that the counter is now shared.

Session-aware cross context data sharing

Didn't you spot anything weird?

I'm sharing data using ServletContext. Its scope is the application scope, not the session scope.

If you open both pages in different browsers you will see that the counter shares its value.

How to make it session-aware?

Since JSESSIONID is the same, you can create a map and use session id as a key to store session data and then store the map in ServletContext like this:
view sourceprint?1.Map<String, Object> data = new HashMap<String, Object>();
2.String id = request.getSession().getId();
3.data.put(id, counter);
4.siblingContext.setAttribute("data", data);

URL: http://jee-bpel-soa.blogspot.com/2009/06/session-sharing-in-apache-tomcat.html
内容概要:本文系统介绍了算术优化算法(AOA)的基本原理、核心思想及Python实现方法,并通过图像分割的实际案例展示了其应用价值。AOA是一种基于种群的元启发式算法,其核心思想来源于四则运算,利用乘除运算进行全局勘探,加减运算进行局部开发,通过数学优化器加速函数(MOA)和数学优化概率(MOP)动态控制搜索过程,在全局探索与局部开发之间实现平衡。文章详细解析了算法的初始化、勘探与开发阶段的更新策略,并提供了完整的Python代码实现,结合Rastrigin函数进行测试验证。进一步地,以Flask框架搭建前后端分离系统,将AOA应用于图像分割任务,展示了其在实际工程中的可行性与高效性。最后,通过收敛速度、寻优精度等指标评估算法性能,并提出自适应参数调整、模型优化和并行计算等改进策略。; 适合人群:具备一定Python编程基础和优化算法基础知识的高校学生、科研人员及工程技术人员,尤其适合从事人工智能、图像处理、智能优化等领域的从业者;; 使用场景及目标:①理解元启发式算法的设计思想与实现机制;②掌握AOA在函数优化、图像分割等实际问题中的建模与求解方法;③学习如何将优化算法集成到Web系统中实现工程化应用;④为算法性能评估与改进提供实践参考; 阅读建议:建议读者结合代码逐行调试,深入理解算法流程中MOA与MOP的作用机制,尝试在不同测试函数上运行算法以观察性能差异,并可进一步扩展图像分割模块,引入更复杂的预处理或后处理技术以提升分割效果。
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值