| sumanthnath gangavarapu, there isn't enough information in your report to perform a meaningful diagnosis. A ClosedChannelException merely indicates that the channel the agent and master were communicating on has been closed. Nothing in the report provides any indication as to how or why the channel was closed. Generally, these sorts of failures are due to system or environment issues. It isn't a problem in the code but something external that causes the connection to close. You should investigate your systems and networks so that you can isolate and determine the cause of the failure. A short, abbreviated sample of the things you should examine:
- Check agent logs.
- Check master logs.
- Check system logs, such as Windows Event logs.
- Look for high resource usage (CPU, disk, network, etc.) on master and agent machines.
- Investigate network issues.
- Look for any commonalities among the failures such as
- Time of day
- Duration of job
- Operating system
- System uptime
- Check the health and logs of the hosting environments.
- Match all of the timestamps and events up together with the failures to try and develop a picture of what is occurring.
As a simple example, I saw some similar behavior on my Windows machine when it decided it was time to go to sleep. (Windows server OSes don't usually have this behavior.) I'm sorry that I'm not able to solve this problem for you, but the investigation needs to be performed at your end. If you manage to figure out the cause, I'd be curious to learn what you discovered. |
