The CTT node cache building routine enters an infinite loop when it encounters a Node that has too many references, which causes encoding limits to be exceeded, which causes a reconnect where it tries again - and this repeats.

Alex debugged it, here's his email:

Issue
The problem are the inverse HasTypeDefinition references from the BaseDataVariableType. In your demo server with the mass folder there are over 100.000 references in the browse:

image001.jpg
This is then resulting in a BadEncodingLimitsExceeded in the CTT:
image002.png
Because of this problem the CTT throws away the connection and guess what, retries in the hope the problem is now gone. This is the endless loop that you are seeing. No question, this is an issue in the CTT when building the offline cache. If you could create a mantis for this, it would be appreciated otherwise I’ll create one. But usually, it is better if the issue is reported by a vendor not by the developer doing the work �

Workaround:
With the current version of the CTT you have 2 options to work around the issue:
Add the BaseDataVariableType to the UaNodesToIgnore. With this the CTT doesn’t try to get these references, and you should be good.
Set the MaxReferencesToReturn in your server settings, so the CTTs limits are not exceeded.