Hello Community,
I have encountered several scenarios when troubleshooting my SP 2013 farm that were resolved by recycling the STS App Pool. The most obvious indication that this needs to be done is a reading in the ULS logs that looks like:
"An exception occurred when trying to issue security token: The server was unable to process the request due to an internal error. For more information about the error, either turn on IncludeExceptionDetailInFaults (either from ServiceBehaviorAttribute or from the <serviceDebug> configuration behavior) on the server in order to send the exception information back to the client, or turn on tracing as per the Microsoft .NET Framework SDK documentation and inspect the server trace logs.." with a more useful message typically preceding that reads:
"SPSecurityContext: Request for security token failed with exception: System.ServiceModel.FaultException: The server was unable to process the request due to an internal error...."
When Web Apps are provisioned, SP automatically configures them to be recycled at various times (non-overlapping for mirrored app pools on load balanced WFEs). My question is as follows:Why doesn't SP take this step for the STS or any other Service App Pool? I want to institute a recycle schedule for STS to fix any issues that force the service to become unresponsive or drop communication with whichever requester isn't able to receive tokens, but I need to understand the reasoning/potential impacts before taking this step. Any help would be greatly appreciated!!
Thanks in advance for all who respond,
Jason Chmiel
