https://issues.apache.org/bugzilla/show_bug.cgi?id=47298
Summary: enabled emptysessionpath not checking if route
replacement is needed
Product: Tomcat 6
Version: 6.0.18
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: Catalina
AssignedTo: [email protected]
ReportedBy: [email protected]
Hi, our app currently relies on using the attribute emptysessionpath=true on
the ajp connector due to having most of our
urls not containing the context path of our web app.
We are having trouble with the jvmroute switching as the Tomcat code doesn't
appear to
check if the jvmroute is valid for that node? I noticed in the
org.apache.catalina.session.ManagerBase there is some code that is
commented out, which would fix the route replacement.
Is it possible to uncomment the route replacement check below in ManagerBase?
code from ManagerBase:
if (sessionId == null) {
sessionId = generateSessionId();
// FIXME WHy we need no duplication check?
/*
synchronized (sessions) {
while (sessions.get(sessionId) != null) { // Guarantee
// uniqueness
duplicates++;
sessionId = generateSessionId();
}
}
*/
// FIXME: Code to be used in case route replacement is needed
/*
} else {
String jvmRoute = getJvmRoute();
if (getJvmRoute() != null) {
String requestJvmRoute = null;
int index = sessionId.indexOf(".");
if (index > 0) {
requestJvmRoute = sessionId
.substring(index + 1, sessionId.length());
}
if (requestJvmRoute != null &&
!requestJvmRoute.equals(jvmRoute)) {
sessionId = sessionId.substring(0, index) + "." +
jvmRoute;
}
}
*/
}
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]