I think we're going to need a customer that can reproduce the issue on one of the patches where it is supposed to be resolved. I verified both notes are set to release to customer. I think it's something in the tomcat cache that causes the issue and that has been a sure way to clean it out. If the issue occurs more often and you cannot resolve with clearing the tomcat cache, or disabling FIPS then I'd recommend raising a case with deployment or admin to investigate further.
Regards,
Tim