IdPv3 Issues with non-closed browsers

[Cantor, Scott]

On 9/15/15, 7:11 AM, "users on behalf of Callum Smith" <users-bounces at shibboleth.net on behalf of callum at strubi.ox.ac.uk> wrote:

>Running latest IdP v3.1.2 on Tomcat 8.
>Service sits behind reverse proxy over ajp
>OpenJDK 1.7.0_85 on CentOS 5.11
>No errors in the logs.

I don't know how to diagnose it if there's no error. The container's not logging anything?

>The server does run memcached with a paired node, both nodes have the IdP setup and running, with the second server set up as a hot swap by the front-end reverse proxy. This feels like the potential cause of issues, should I be looking to change the shibboleth storage engine to something on the disk?

Don't have any familiarity with memcache. My advice is always to use client side sessions, not server-side state. Unless you absolutely have to have it, there's no advantage to it.

Since nobody has reported anything like that with the default configuration, I would tend to assume it's storage related.

-- Scott