Handle java exceptions
- Dominant language
- Python
- Stars
- 4
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
While srm starts the transfer some errors may occur, e.g. site is timed out. I need to handle this somehow and try another site. Here is an example of recent error from FM logs when FNAL has been cut off:
{{{
SRMClientV2 : srmPrepareToGet: try # 1 failed with error
SRMClientV2 : ; nested exception is:
java.net.ConnectException: Connection timed out
Sat Oct 15 15:25:24 CEST 2011: java.net.ConnectException: Connection timed out
Sat Oct 15 15:25:24 CEST 2011: stopping copier
going to stop....
Exception in thread "main" java.lang.Exception: stopped
at gov.fnal.srm.util.Copier.run(Copier.java:287) at java.lang.Thread.run(Thread.java:595)
Sat Oct 15 15:25:24 CEST 2011: stopping copier
ERROR:FileManager:Transfer has already been launched!Traceback (most recent call last):
File "/data/srv/be1109h/sw/slc5_amd64_gcc434/cms/filemover/1.0.9/lib/python2.6/site-packages/fm/core/Fi
leManager.py", line 128, in status status = self.lfn_requests[lfn].status()
File "/data/srv/be1109h/sw/slc5_amd64_gcc434/cms/filemover/1.0.9/lib/python2.6/site-packages/fm/core/Fi
leMover.py", line 122, in status
self.start() File "/data/srv/be1109h/sw/slc5_amd64_gcc434/cms/filemover/1.0.9/lib/python2.6/site-packages/fm/core/FileMover.py", line 84, in start raise Exception("Transfer has already been launched!")Exception: Transfer has already been launched!
}}}
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.