Comments (2)
  • Add a Comment
  • Edit
  • More Actions v
  • Quarantine this Entry

1 DougBreaux commented Permalink

<p>BTW, we recently noticed a specific case where the Cache ID changed for a Session: when the Session hadn't been accessed in a long time. In fact, the subsequent access was right before the 30-minute timeout would have triggered.</p> <p>One interesting behavior we observed in this case was that an object on the Session which we had been comparing for identity-equivalence (== comparison) was no longer equivalent after the Cache ID changed. We needed to update our code to use .equals() instead (which we should have been using the in the first place, anyway).</p>

2 lherrera_mx commented Permalink

Great investigation Doug!!!... It helped me a lot!... I just tweeted in @WebSphereMex... =)