<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Dec 10, 2014 at 7:36 PM, Cantor, Scott <span dir="ltr"><<a href="mailto:cantor.2@osu.edu" target="_blank">cantor.2@osu.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><span class="">On 12/11/14, 2:22 AM, "James Nurmi" <jdnurmi@qwe.cc> wrote:<br></span><span class="">>2014-12-11 02:04:56 DEBUG XMLTooling.StorageService [12]: updated<br>
>expiration of valid records in context<br>
>(_8ffdfea62caae74a5c1d22260859a983) to (1418267096)<br>
>2014-12-11 02:04:56 DEBUG Shibboleth.Listener [12]: dispatching message<br>
>(remove::StorageService::SessionCache)<br>
>2014-12-11 02:04:56 INFO Shibboleth.SessionCache [12]: remove session::<br>
>(ID: _8ffdfea62caae74a5c1d22260859a983)<br>
<br>
</span>That sequence there basically means the session just wasn't valid. The<br>
usual reason for that would be IP addresses changing. </blockquote><div><br></div><div><div><br class="">Brilliant!</div><div><br></div><div>[For others who may eventually search and find this thread]:</div><div><br></div><div>While the client instance was consistent, and the SP instance was a singleton, the deployment used an ELB from amazon (and a CDN), which tended to permit demuxing through multiple machines (source-IP's) - which is why it was only problematic across various connections counts in the logs - any connection's that got re-used was invariably from the same source machine, when it changed connections, it was usually a different one, so the session got mostly silently invalidated.</div><div><br></div><div>Setting consistentAddress="false" fixed the immediate issue, while I consider more effective solutions.</div></div><div><br></div><div>Appreciate the support, begrudged it may have been :-)</div><div><br></div><div>-James</div><div><br></div><div><br></div></div></div></div>