Status of BF builds started in RTC doesn't get updated.

I have reviewed content of 227986 and the symptoms in general indeed seem to describe my case, i.e. following a reboot of our RTC server my builds have their statuses updated for about a day and then things stop working. What I am not clear about is how do I get the issue resolved... there was a suggestion in 227986 that this could be caused by sharing  a BF userid between different RTC instances  but I verified that is not a case in my scenario. Is it still possible that I could be running into the problem described in 227986 without using shared userids? If so, is the only solution to upgrade to a release containing fix for 227986? We are currently using RTC 4.0,what would be the "closest" release containing the fix?

In case it may be relevant... in our environment we have several build engines defined in two RTC instances (one RTC instance is at 4.0 and the other at 3.0.1.1) which are  accessing a single BF server (7.1.3.2). We don't share userids between the instances but we share userids between build engines within a single instance.

There is not really any workaround for this.  The problem is we can hit an exception during the cache reaping that blocks further event processing.  The fix for the defect will be in 4.0.1. 

In the release notes for 4.0.0.1  I found the following work item listed as one of fixes included in the release:

FYI, recently we upgraded our RTC server to 4.0.0.1 and that resolved the issue, thanks for pointing out the cause of the problem.