Removing a sequence of repositories may lead to "A repository with the name <repository name> does not exist"

Summary

When deleting multiple repositories in a short time frame, the "A repository with the name <repository name> does not exist" is presented in the user interface.
These messages are harmless and are not representing any real issue, they are only temporary and will be resolved by a refresh.

Steps to Reproduce

Note: we have not been able to reproduce this in our labs, but it appears to happen when deleting a sequence of repositories in a short time frame.
The total number of repositories may also be a significant factor.

Expected Results

No error messages are shown in the user interface.

Actual Results

The following message is shown as an error in the user interface:

"A repository with the name <repository name> does not exist"

The below exception is thrown in the atlassian-fisheye-yyyy-mm-dd.log file:

WARN [<thread_id>] / ContextHandler$Context-log - Exception while dispatching incoming RPC call
com.google.gwt.user.server.rpc.UnexpectedException: Service method 'public abstract com.atlassian.fecru.gwt.admin.shared.repositories.RepositoryOperationalSummary com.atlassian.fecru.gwt.admin.client.RepositoryAdminRpcService.getRepositoryOperationalSummary(java.lang.String) throws com.atlassian.fecru.gwt.admin.shared.AuthorizationException,com.atlassian.fecru.gwt.admin.shared.OperationFailureException,com.atlassian.fecru.gwt.admin.shared.NoSuchRepositoryException' threw an unexpected exception: org.apache.xmlbeans.impl.values.XmlValueDisconnectedException

Workaround

Not available.