We've got a case where we automatically generate node names that can become longer than about 220 characters. This seems to be no problem in the author instance, but the activation of such a node fails with the exception shown in attached stacktrace.

One can reproduce the issue in the JCR browser of the author instance by creating e.g. a datafolder with a name that is at least 221 characters long. A subsequent activation will fail.

The problem seems to be that some temporary file names that get created in BaseSyndicatorImpl contain the node name, but there is no check which ensures that the complete filename is shorter than the maximum of 255 characters supported by most filesystems.