Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Insert record failed Violation of PRIMARY KEY constraint with ODBC plugin

Description

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.

Environment

Windows 2008 R2 on Azure.

Attachments

2
  • 09 Oct 2012, 03:51 PM
  • 28 Sep 2012, 05:17 PM

Activity

Show:

Scott Cantor December 10, 2012 at 7:13 PM

Closing with release.

Scott Cantor October 9, 2012 at 3:51 PM

Patched DLLs for the shibsp libraries and the odbc-store plugin.

To use these, make sure both the IIS half and the shibd half are using these new versions, because some of the other bug fixes have affected the RPC messages in a couple of cases.

We shouldn't need any other updates to the rest of the files, but we'll see how they behave.

Paul Brears October 9, 2012 at 2:26 PM

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.

Scott Cantor October 9, 2012 at 2:01 PM

I don't have a complete build I can give you, but I can attach modified DLLs if you're willing to try them.

Have you observed this behavior outside of running load testing scripts?

Paul Brears October 9, 2012 at 8:03 AM

If you've a fixed build that you'd like me to put in my Azure test rig and let it run overnight I can do.

I'd got a webisoget script that could break it reasonably well.

Paul

Fixed
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Components

Fix versions

Affects versions

Created September 28, 2012 at 4:58 PM
Updated December 10, 2012 at 7:13 PM
Resolved October 9, 2012 at 3:13 AM

Flag notifications