我有数据存储和hibernate的问题,我已经能够在localhost中集成Gae + Struts2 + Spring3 + Hibernate4 + MySQL,一切似乎都有效,但是当我尝试在HTTP中创建会话时,会话不是created或session.getLastAccessedTime()始终为1970-01-01(默认值)。当我转到http:localhost:8080 / _ah / admin中的数据存储区链接时,没有创建会话。
我使用ESAPI作为安全性和此方法:
public boolean isSessionTimeout() {
HttpSession session = ESAPI.httpUtilities().getCurrentRequest().getSession(false);
if (session == null)
return true;
Date deadline = new Date(session.getLastAccessedTime() + IDLE_TIMEOUT_LENGTH);
Date now = new Date();
return now.after(deadline);
}
总是返回true。
我在appengine-web.xml中启用了会话,只要这种配置在tomcat中工作,但在appengine版本1.9.2中存在某种问题,我不理解这个问题。
我在maven中构建项目如下:
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<version>2.5.1</version>
<artifactId>maven-compiler-plugin</artifactId>
<configuration>
<source>1.7</source>
<target>1.7</target>
</configuration>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-war-plugin</artifactId>
<version>2.3</version>
<configuration>
<archiveClasses>true</archiveClasses>
<webResources>
<!-- in order to interpolate version from pom into appengine-web.xml -->
<resource>
<directory>${basedir}/src/main/webapp/WEB-INF</directory>
<filtering>true</filtering>
<targetPath>WEB-INF</targetPath>
</resource>
</webResources>
</configuration>
</plugin>
<plugin>
<groupId>com.google.appengine</groupId>
<artifactId>appengine-maven-plugin</artifactId>
<version>${appengine.app.version}</version>
<configuration>
<jvmFlags>
<jvmFlag>-Dappengine.generated.dir=${project.basedir}/appengine</jvmFlag>
<jvmFlag>-Ddatastore.backing_store=${project.basedir}/local_db.bin</jvmFlag>
</jvmFlags>
</configuration>
</plugin>
</plugins>
</build>
我的web.xml中有第一个过滤器,ESAPIFilter包含:
public void doFilter(ServletRequest req, ServletResponse resp, FilterChain chain) throws IOException {
HttpServletRequest request = (HttpServletRequest) req;
HttpServletResponse response = (HttpServletResponse) resp;
try {
ESAPI.httpUtilities().setCurrentHTTP(request, response);
} catch (Exception e) {
logger.error(Logger.SECURITY_FAILURE, "Error in ESAPI security filter: " + e.getMessage(), e);
}
try {
// figure out who the current user is
try {
ESAPI.authenticator().login();
} catch (AuthenticationException e) {
request.setAttribute("message", "Unauthorized");
}
// log this request, obfuscating any parameter named password
ESAPI.httpUtilities().logHTTPRequest(request, logger, Arrays.asList(obfuscate));
// check access to this URL
if (!ESAPI.accessController().isAuthorizedForURL(request.getRequestURI())) {
request.setAttribute("message", "Unauthorized");
}
// check for CSRF attacks
//ESAPI.httpUtilities().verifyCSRFToken(request);
// forward this request on to the web application
chain.doFilter(request, response);
// set up response with content type
ESAPI.httpUtilities().setContentType(response);
// set no-cache headers on every response
// only do this if the entire site should not be cached
// otherwise you should do this strategically in your controller or actions
ESAPI.httpUtilities().setNoCacheHeaders(response);
} catch (Exception e) {
logger.error(Logger.SECURITY_FAILURE, "Error in ESAPI security filter: " + e.getMessage(), e);
request.setAttribute("message", e.getMessage());
} finally {
// VERY IMPORTANT
// clear out the ThreadLocal variables in the authenticator
// some containers could possibly reuse this thread without clearing the User
try {
ESAPI.clearCurrent();
} catch (Exception e) {
logger.error(Logger.SECURITY_FAILURE, "Error in ESAPI security filter: " + e.getMessage(), e);
}
}
}
答案 0 :(得分:0)
最后我发现问题不知何故会话是用默认的session.getLastAccessedTime()= 0创建的,我用这样的当前时间设置了这个值:
public boolean isSessionTimeout() {
HttpSession session = ESAPI.httpUtilities().getCurrentRequest().getSession(false);
if (session == null)
return true;
long lastAccessedTime=System.currentTimeMillis();
if(session.getLastAccessedTime()!=0){
lastAccessedTime=session.getLastAccessedTime();
}
Date deadline = new Date(lastAccessedTime + IDLE_TIMEOUT_LENGTH);
Date now = new Date();
return now.after(deadline);
}
最后现在一切正常,我可以在本地创建一个会话,我还没有在生产中尝试过。