session identifiers for DSO session enabled apps under websphere always use
default cacheId
-------------------------------------------------------------------------------------------
Key: CDV-258
URL: https://jira.terracotta.org/jira//browse/CDV-258
Project: Community Development
Issue Type: New Feature
Reporter: Tim Eck
Assigned To: Issue Review Board
It's not actually clear what the effect of this is...
The format of the session identifier for a websphere app looks like it has
three components:
1) The first 4 characters are some sort of cache ID that might have something
to do with websphere's dynacache stuff
2) The real session identifier
3) a server identifier (aka cloneID)
For the time being we are ignoring component #1 and using the "default" cacheId
of "0000". This item is the reminder to get to the bottom of it. The terracotta
class that generates session IDs should have a way to specify the cacheID, but
there won't be any instrumentation to hook it up to a "real" value under we
understand what it means and where it comes from
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.terracotta.org/jira//secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
tc-dev mailing list
[email protected]
http://lists.terracotta.org/mailman/listinfo/tc-dev
