https://bugzilla.mcs.anl.gov/swift/show_bug.cgi?id=1347 --- Comment #3 from Mihael Hategan <[email protected]> 2014-11-01 01:28:46 --- It looks like the timeouts occur after workers are shut down, which is to be expected. Here's an example for the first two timeout exceptions in the coaster log, but all I checked are like that: 2014/10/11 11:25:10.000 INFO 000000 Acknowledged shutdown. 2014/10/11 11:25:10.000 INFO 000000 Ran a total of 560 jobs 2014/10/11 11:25:11.000 INFO 000000 Exiting 2014-10-11 16:27:11,186+0000 INFO ChannelContext Notifying commands and handlers about exception org.globus.cog.coaster.TimeoutException: Channel timed out. lastTime=141011-162510.870, now=141011-162711.185, channel=TCPChannel [type: server, contact: 1011-3403290-000001-000000] ----------------------- 2014/10/11 11:25:13.000 INFO 000000 Acknowledged shutdown. 2014/10/11 11:25:13.000 INFO 000000 Ran a total of 560 jobs 2014/10/11 11:25:14.000 INFO 000000 Exiting 2014-10-11 16:27:14,187+0000 INFO ChannelContext Notifying commands and handlers about exception org.globus.cog.coaster.TimeoutException: Channel timed out. lastTime=141011-162513.871, now=141011-162714.187, channel=TCPChannel [type: server, contact: 1011-3403290-000000-000000] ----------------------- I committed (r4045) a patch to disable the timeout checks when a channel is closed. So unless there is another error here that I'm missing, I would close this as not much of a bug. -- Configure bugmail: https://bugzilla.mcs.anl.gov/swift/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.