[JIRA] Commented: (SSPCPP-507) Insert record failed Violation of PRIMARY KEY constraint with ODBC plugin

[pbrears@idp.protectnetwork.org (JIRA)]

    [ https://issues.shibboleth.net/jira/browse/SSPCPP-507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14442#comment-14442 ] 

pbrears at idp.protectnetwork.org commented on SSPCPP-507:
-------------------------------------------------------

I've done some further investigation.

I can only reproduce this with two things happening:
Firstly there must be two servers in the cluster; i've not been able to make this fail when in single server mode. (although sometimes it can take a while to fail so I might not have left enough time)
Secondly I can only get this to fail when logout from the IdP isnt' happening properly between sessions and it's being hit with the same user. (see #508)

By turning off maintainReverseIndex the problem goes away.

This was the failing config in Shibboleth2.xml
SessionCache type="StorageService" StorageService="db" cacheAssertions="false" cacheTimeout="3600" inprocTimeout="900" cleanupInterval="900" 

I'd noticed that the version number on the namedID record increased for each logon and would eventually have exceeded the value being an smallint if the primarykey issue hadn't killed shibd first; (I assume the excludeReverseIndex is designed to stop test users crashing the system, or should it have wrapped when it exceeded smallint?)
  
Is there anything else I can try to help narrow down the issue from here?

Paul


> Insert record failed Violation of PRIMARY KEY constraint with ODBC plugin
> -------------------------------------------------------------------------
>
>                 Key: SSPCPP-507
>                 URL: https://issues.shibboleth.net/jira/browse/SSPCPP-507
>             Project: Shibboleth SP - C++
>          Issue Type: Bug
>      Security Level: Standard(Standard bug, may impact functionality but does not represent a security vulnerability ) 
>          Components: Session Cache
>    Affects Versions: 2.5.0
>         Environment: Windows 2008 R2 on Azure.
>            Reporter: pbrears at idp.protectnetwork.org
>            Assignee: Scott Cantor
>              Labels: Session
>         Attachments: shiblogs.zip
>
>
> Using two servers with the odbc connection plugin for the storage service you can occasionally get 'insert record failed' 'Violation of PRIMARY KEY constraint' logged
> We're using "SQL Server Native Client 10.0" driver to access SQL azure for the db
> There are two servers in the non sticky load balancer. It's likely that /SAML/POST and /Secure are landing on different boxes.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira