Upgrade to Traveler 16 freezing users out

I am wandering if anyone else has experienced issues with the Traveler update to 9.0.1.16. Since upgrading we have had to restart the server repeatedly as it freezes users out (not all users). Those that get forzen out Traveler registers them as syncing to the server but phone not showing anything

It seemed to be doing it when certain regions had connection issues to the home mail server, All South Africa users stopped working until we restarted the Traveler server it almost as if the connection goes it just stops responding, wont come back on until restarted. Same thing has happened to our Middle East sites this week and then to our UK ones today. This server never missed a beat until we applied this fix pack?

Is there an setting that we need to apply or is it worth just rolling back to last working fix pack (8) that we were using?

Any pointers would be much appreciated before I raise a PMR?

Thanks

Mark

Subject: Do the affected sites have clustered mail servers or standalone mail servers?

My reading of the technote is that both members of an email cluster must be seen as unreachable for all users’ devices to be disabled. Have you tried the workaround suggested in the technote (restarting the Traveler server once connectivity to the mail servers has been confirmed)?

Subject: LO91723 fixed with 9.0.1.17

There is indeed a known error with 9.0.1.16 where users are “frozen”, when their mailserver has been restarted.

http://www-01.ibm.com/support/docview.wss?uid=swg1LO91723 http://www-01.ibm.com/support/docview.wss?uid=swg1LO91723

Supposedly this is fixed in 9.0.1.17. I did not have the time to test, yet.