Why does my Site Migration keep failing with a java.lang.StackOverflowError?
This is typically due to the application having to deal with a very large version chain for a particular asset. In many cases, this problem can be resolved by taking the following action:
- If using Linux/nix or the Windows command line, change the Xss value to 8M per the documentation here. If using the Windows service, change the Thread stack size* field to 8000 KB per the documentation here
- Once Cascade Server has been restarted, attempt the Site Migration again to see if the problem has been resolved
- Once the Site Migration has completed successfully, remove the Xss/Thread stack size parameter so that the default values will be restored upon the next restart of Cascade Server