Tomcat crash after windows update on 2016

update: windows update ended up not being the issue.  After some more digging this issue was with SCCM Software update express port being set to 8005.  This caused a conflict with the Tomcat server.  having the SCCM admin change the port has stopped the crash.  I am going to leave this post so other can find it but you should skip the parts about windows update/KBs.

I have WMS installed in 2 server 2016 boxes.  One in production and one in test.  both of them failed after KB4465659 was installed on them as tomcat crashes when the web server is accessed.  Prod is running 1.1 but I have tested and see the same issue with 1.2,1.3, and now 1.4.

I am getting the errors in the stratus logs that seems to point to issues comunicating with the memcached server.  All services will come up but then the tomcat services stop after the errors.

2019-05-30 11:42:29,855 [ERROR] Thread-9 Unable to read from cache. Shutting down
2019-05-30 11:42:29,856 [ERROR] Thread-9 Unable to read from cache.Shutting down
2019-05-30 11:42:29,858 [INFO] Thread-9 AppServerQueueArbitrator not found in cache, adding to cache.
2019-05-30 11:42:29,858 [ERROR] Thread-9 Unable to add to cache. Shutting down
2019-05-30 11:42:29,859 [ERROR] Thread-9 Unable to write to cache.Shutting down
2019-05-30 11:42:29,872 [INFO] Thread-9
+++ active ServersInCluster during rebalance +++
2019-05-30 11:42:29,877 [WARN] Thread-9 Cache exeception :
java.lang.IllegalStateException: Shutting down
at net.spy.memcached.MemcachedConnection.checkState(MemcachedConnection.java:824)
at net.spy.memcached.MemcachedConnection.enqueueOperation(MemcachedConnection.java:640)
at net.spy.memcached.MemcachedClient.asyncGet(MemcachedClient.java:841)
at net.spy.memcached.MemcachedClient.get(MemcachedClient.java:1003)
at net.spy.memcached.MemcachedClient.get(MemcachedClient.java:1024)
at com.wyse.stratus.server.cache.CacheableItem.get(CacheableItem.java:63)
at com.wyse.stratus.server.cache.MessageQueueProcessorLoad.getMQPLoad(MessageQueueProcessorLoad.java:28)
at com.wyse.stratus.server.bo.queue.AppQueueSchedulerImpl.constructServersInCluster(AppQueueSchedulerImpl.java:619)
at com.wyse.stratus.server.bo.queue.AppQueueSchedulerImpl.rebalanceQueues(AppQueueSchedulerImpl.java:323)
at com.wyse.stratus.server.bo.queue.AppQueueSchedulerImpl.scheduleQueues(AppQueueSchedulerImpl.java:227)
at com.wyse.stratus.server.bo.queue.AppQueueSchedulerImpl.run(AppQueueSchedulerImpl.java:141)
at java.base/java.lang.Thread.run(Thread.java:834)

Has anyone had issues like this or is there something in my environment that is causing this issue to crop up?