Intermittent Request Failure with status 101 in cluster environment

Document ID : KB000112990
Last Modified Date : 04/09/2018
Show Technical Document Details
Issue:
Intermittent Request Failure with status 101 in cluster environment
Environment:
catalog 17.1  ro catalog 17.1 with rollup1 patch 
Cause:
Customers who upgraded to 17.1 from previous versions and having cluster environment (more than one node, it can be via load balancing…etc.), they may encounter “request not getting submitted” issue with below error: 
com.microsoft.sqlserver.jdbc.SQLServerException: Violation of PRIMARY KEY constraint 'XPKusm_subscription_detail'. Cannot insert duplicate key in object 'dbo.usm_subscription_detail'. The duplicate key value is (51739). 
at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:217) 
at com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(SQLServerStatement.java:1635) 

Here even they submitted request it will be in “Not-submitted” state (101) 
This is an Intermittent issue. If they re-start all the nodes issue will get resolve.

 
Resolution:
 It is a bug , which  is  addressed by the testfix   T6D9388   (  Its pre-requisites  are  17.1 Rollup1 + T6D9385 )  .   You can contact CA support via support case to get    T6D9385  and T6D9388  .

Both T6D9385  and T6D9388  will be rolled into next rollup patch : 17.1 rollup2  ( which will be published and available to download  Nov  2018 )