[
https://jira.jboss.org/jira/browse/JBAS-7116?page=com.atlassian.jira.plug...
]
Brian Stansberry updated JBAS-7116:
-----------------------------------
Workaround Description:
Don't include the domain in the server.xml jvmRoute value; just use a distinct node
name for each node. The mapping from node name to domain can be specified in the mod_jk or
mod_cluster load balancer configuration and doesn't need to be included in the
jvmRoute itself.
For configuring the domain with mod_jk, see the "domain" directive on
http://tomcat.apache.org/connectors-doc/reference/workers.html.
For mod_cluster, see the "domain" attribute at
http://www.jboss.org/mod_cluster/java/properties.html#proxy
Workaround: [Workaround Exists]
Improper handling of domain included in jvmRoute
------------------------------------------------
Key: JBAS-7116
URL:
https://jira.jboss.org/jira/browse/JBAS-7116
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Clustering, Web (Tomcat) service
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Fix For: JBossAS-5.2.0.Beta1, JBossAS-6.0.0.Alpha1
org.jboss.web.tomcat.service.session.Util doesn't handle a domain.node as the
jvmRoute format:
public static String getRealId(String sessionId)
{
int index = sessionId.lastIndexOf("."); // WRONG!! Use
String.indexOf('.', 0);
if (index > 0)
{
return sessionId.substring(0, index);
}
else
{
return sessionId;
}
}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira