Hi, We're using tomcat with clustering enabled for session replication purposes. This is all well and good and works fine.
However, in addition I wanted to set the sessionId length to something shorter than the default. If it wasn't for the clustering I would simply provide a context.xml file in the webapp with a suitable Manager node, eg: <Context> <Manager sessionIdLength="6"/> </Context> and all would be fine. The trouble is that by doing this the session manager that would normally be created by the Cluster configuration is overridden by this Manager definition. Unless I'm missing something (and I've had a glance through the source code as well), I can't see any way of controlling any of the session manager attributes when the session manager is created using a Cluster definition. Since all you appear to be able to do is specify the manager class name and let it use whatever defaults are in play for that manager. Am I missing something? Regards, Mark ________________________________________________________________________ This email has been scanned for all known viruses by the MessageLabs SkyScan service. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
