The issue we are seeing is identical to the one discussed here. The problem is the listed resolution to that issue is to upgrade to version 2.11.2.2 or later and we are having the issue show up after ...