Arun,
With the information we have so far, the only recommendations that we can really make would be:
- Upgrade to 4.5 - this is the latest release and includes many fixes (and new functionality)
- Ensure your system meets our documented requirements.
- Increase both the initial and max java heap size for the portal process. Instructions can be found here:
Increasing CA TDM Portal JVM memory - CA Knowledge - If the TDM server is VM, you may want to discuss with your VM admin to increase shares of CPU/memory for this host. This doesn't change the resource allocation (16 gigs is still 16 gigs & 4 CPUs is still 4 CPUs), but it does give the VM in question priority over other VMs with a lower number of shares.
- If you see that the system is bottlenecked on a specific resource (total CPU utilization at 100% or memory extremely high), request an increase in resources accordingly.
Our minimum requirements for a TDM Server is 16 gigs of RAM and 4 CPU cores. It's possible that if you have too much load on the system in general, you many need to increase the specs of the system accordingly - our high volume recommendations would be 32 gigs of ram and 8 CPU cores.
Assuming that you have at least the minimum requirements, if there is available memory on the system, and if the job is memory intensive, Portal can benefit greatly from an increased heap size per the above document.