shibpid serializable transactions

[Charles R. Tompkins]

Hi All,

I'm running into an issue with "shibpid" transactions in a multi-appnode
environment using Shib IdP v3.2.1 and an Oracle DB backend.

Shibpid inserts are generating errors (ORA-08177 can't serialize access for
this transaction) as other nodes update the table out from underneath the
transaction in error state.  Thankfully, adding ample transactionRetries and
adding "72000" to retryableErrors has limped me through this issue.

Looking at the source code
(http://svn.shibboleth.net/view/java-identity-provider/tags/3.2.1/idp-saml-i
mpl/src/main/java/net/shibboleth/idp/saml/nameid/impl/JDBCPersistentIdStoreE
x.java?view=markup), line 777 contains
"conn.setTransactionIsolation(Connection.TRANSACTION_SERIALIZABLE)".

What is the reasoning behind making the transaction isolation level
serializable for these transactions?  It's not easily agreeing with my
multimode environment.

Thanks!

Charles Tompkins
UF Information Technology


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4793 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/users/attachments/20160306/b49bd58e/attachment-0001.p7s>