|
Mantis - Resin
|
|||||
| Viewing Issue Advanced Details | |||||
|
|
|||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 706 | minor | always | 01-05-06 11:08 | 01-30-06 16:18 | |
|
|
|||||
| Reporter: | ferg | Platform: | |||
| Assigned To: | ferg | OS: | |||
| Priority: | normal | OS Version: | |||
| Status: | closed | Product Version: | 3.0.17 | ||
| Product Build: | Resolution: | fixed | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | 3.0.18 | ||
|
|
|||||
| Summary: | 0000706: alternate SESSIONID generation | ||||
| Description: |
(rep by Serge Knystautas) The new Apache HTTPD 2.2 has load balancing and stickysession capability by building onto the mod_proxy capabilities, which I'm trying to take advantage of. The problem is that their stickysession capabilities is heavily reliant on how Tomcat generates JSESSIONID. Instead of prepending the session ID with the srun index, they append a '.' and then the srun index (or route as they call it). Would it be possible to have a setting to specify how JSESSIONID's are generated? It looks like the change would be isolated to com.caucho.server.session.SessionManager since that handles generating the session ID and determining whether this is in this session group. |
||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Relationships | |||||
| Attached Files: | |||||
| Notes | |||||
|
|
|||||
|
|
||||