[JIRA] Commented: (SSPCPP-507) Insert record failed Violation of PRIMARY KEY constraint with ODBC plugin
pbrears@idp.protectnetwork.org (JIRA)
noreply at shibboleth.net
Tue Oct 9 10:28:21 EDT 2012
[ https://issues.shibboleth.net/jira/browse/SSPCPP-507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14472#comment-14472 ]
pbrears at idp.protectnetwork.org commented on SSPCPP-507:
-------------------------------------------------------
I can copy the dlls onto the right boxes and give it go.
One of our testers had managed to get it to fail manually, quite quickly, with logon-UserA, partial-logoff, logon-UserB, repeat till fail.
I created the websisoget script based on what was failing with a manual test.
> 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
> Fix For: 2.5.1
>
> Attachments: shiblogs.zip
>
> Time Spent: 4 hours
> Remaining Estimate: 0 minutes
>
> 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
More information about the commits
mailing list