To resolve this issue, first, try recycling the Repository Service.
1. Would it help increasing the resilience time ?
Answer: You can increase the Resilience timeout on the basis of logs.
If you want to increase resilience timeout.
Go to registries-->HKEY_CURRENT_USER-->Software-->Informatica-->PowerCenterClientTools-->10x--> Repository manager-->click on the repository you want to change the resilience for.
Add a new string value ' Client Resilience Timeout' = 600.
Also please make sure the resilience timeout is being changed for the repository in the admin console too. Again, this would only increase the time period for the services trying to connect. If the network glitch/issue is more than this specified time then this will not help.
2. Is it failing because the XML file has too many objects ?
Answer: This error is probably due to the client not able to connect to the repository within the resilience time which is set to 180 seconds. The resilience time can be increased to 600 on both the client and server but this would only increase the time that the client tries connecting to the repository. Please check for your network errors or contact your network admin and see whether there any issues with the network.
3. What could be the reason to crash the server?
Answer: Few possibilities:
- The node could be going down; check catalina.out; then you could increase the HEAP memory if the issue is too frequent. Also, try Tomcat Cleanup.
- On Oracle, you can check Listener.log as well as alert.log to look for any TNS refused/failed connection messages.
- Do a regular cleanup of the repository.
Also, what's the Windows version?
What's the repository DBMS and version?
What database client (in what version) do you use to connect to the repository DB?