jboss eap 6.3 集群(cluster)-Session 复制(Replication)

时间:2023-03-09 17:32:18
jboss eap 6.3 集群(cluster)-Session 复制(Replication)

本文算是前一篇的后续,java web application中,难免会用到session,集群环境中apache会将http请求智能转发到其中某台jboss server。假设有二个jboss server:Server A,Server B,Session值在Server A上。用户在访问某一个依赖session的页面时,如果第一次访问到Server A,能正常取到Session值,刷新一下,如果这时转发到Server B,Session值取不到,问题就来了。

解决的办法简单到让人不敢相信,在app的web.xml中加一行 <distributable /> 即可(前提:jboss cluster是使用mod_cluster实现的),有了这个节点后,向某台server写入session时,session会自动复制到其它server node。

下面来具体验证一下:

网络环境:

jboss eap 6.3 集群(cluster)-Session 复制(Replication)

如上图,有二台机器:172.21.129.181(Master Server & Apacha Server)、172.21.129.128(Slave Server)

User所在的计算机IP为: 172.21.129.57 (图中未标出)

Sample Application:

为了验证,我们建一个最简单的spring mvc web应用

Controller代码如下:

 package com.cnblogs.yjmyzz;

 import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpSession; import org.apache.log4j.Logger;
import org.springframework.stereotype.Controller;
import org.springframework.ui.Model;
import org.springframework.web.bind.annotation.RequestMapping;
import org.springframework.web.bind.annotation.RequestMethod;
import org.springframework.web.servlet.ModelAndView; @Controller
public class HomeController { Logger log = Logger.getLogger(this.getClass()); private static final String sessionKey = "test"; /**
* 写入session
* @param request
* @return
*/
@RequestMapping(value = "/session-write", method = RequestMethod.GET)
public String writeSession(HttpServletRequest request) {
HttpSession session = request.getSession();
session.setAttribute(sessionKey, "sample value");
return "session/write";
} /**
* 读取session
* @param request
* @return
*/
@RequestMapping(value = "/session-read", method = RequestMethod.GET)
public ModelAndView readSession(HttpServletRequest request) {
HttpSession session = request.getSession();
Object sessionValue = session.getAttribute(sessionKey);
ModelAndView model = new ModelAndView();
if (sessionValue != null) {
model.addObject(sessionKey, sessionValue);
} try {
//显示几个IP到页面,用于辅助判断本次Http请求转发到了哪台server
String hostInfo = "InetAddress.getLocalHost() = "
+ java.net.InetAddress.getLocalHost()
+ "<br/>request.getRemoteAddr() = "
+ request.getRemoteAddr() + ":" + request.getRemotePort()
+ "<br/>x-forwarded-for = " + getUserReadIP(request)
+ "<br/>request.getLocalAddr() = " + request.getLocalAddr()
+ ":" + request.getLocalPort();
model.addObject("host", hostInfo); } catch (Exception e) { }
model.setViewName("session/read");
return model;
} // 获取用户真实IP
private String getUserReadIP(HttpServletRequest request) {
if (request.getHeader("x-forwarded-for") == null) {
return request.getRemoteAddr();
}
return request.getHeader("x-forwarded-for");
} }

write.jsp:(写入session)

 <%@ page language="java" contentType="text/html; charset=UTF-8"
pageEncoding="UTF-8"%>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>session write test</title>
</head>
<body>
<h1>Session写入成功!</h1>
</body>
</html>

read.jsp:(显示session)

 <%@ page language="java" contentType="text/html; charset=UTF-8"
pageEncoding="UTF-8"%>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>session read test</title>
</head>
<body>
<h1>Session("test"):${test}</h1>
<h1>${host}</h1>
</body>
</html>

准备就绪,依次以domain模式启动master server、slave server上的jboss,最后启动apache server。

然后访问:

http://172.21.129.181/ModClusterSample/session-write.do 写入session

继续访问:

http://172.21.129.181/ModClusterSample/session-read.do 读取session

jboss eap 6.3 集群(cluster)-Session 复制(Replication)

从输出的几个IP看,本次请求apache转发到了 172.21.129.128上(即:slave Server),user客户端的IP为 172.21.129.57,而apache server的IP为172.21.129.181

另外第一行表明正确读取到了session值:sample value

这时进入master server的jboss控制台,将slave master上的jboss server给stop掉

jboss eap 6.3 集群(cluster)-Session 复制(Replication)

再次刷新user机器上的http://172.21.129.181/ModClusterSample/session-read.do

jboss eap 6.3 集群(cluster)-Session 复制(Replication)

可以看到,因为slave server上的jboss server已经被停掉了,所以本次http请求被转发到了172.21.129.181上(即master server),但是session值仍然能正常输出,说明session值在写入的同时,确实已经被复制到二台jboss server上了,session replication验证成功!