|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
Anil - i think this can be closed. I was finally able to track my issue down to having something to do with jboss session replication. I have not had a chance to re-visit why jboss sessions where not replicating originally (although i did read the link you provided and our config looks ok on the first pass). What i found was that even after we used the F5 to handle sticky sessions, we had left the <distributable/> tag in the web.xml of the idp.war. It appears that after an hour, some sort of session replication event happens which clobbers all the sessions on one of the nodes. Disabling this in the application config solved our problem.
If you want more details let me know, otherwise i am satisfied. thanks for your help