Strange error while downloading file from LFC
I encountered the error pased below in my logs and I cannot figure out what this means. It happens when I try to download a file from LFC, specifically, in the line "remoteEntry.copy(target, flags);". This should not be related to the code, as the application is running on the server for several weeks and nothing was changed in it in the meantime. I thought there could be something wrong with the LFC server or an SE, but they seem to work OK used with command line tools.
Caused by: java.io.IOException: java.io.IOException: class org.ogf.saga.error.DoesNotExistException: org.globus.ftp.exception.UnexpectedReplyCodeException: Custom message: Unexpected reply: 500-Command failed. : System error in name: No such file or directory 500-A system call failed: No such file or directory 500 End.
I also attached the full stack trace.
We are using jsaga-1.0.1, but the same happens on a server with jsaga-1.0.0 and even with jsaga-0.9.15.
Could you figure out what could be wrong with the system by this error?
Thanks in advance,
error.txt (8.67 KB)
It seems that with a new version of DPM, it no longer supports turls in form gsiftp://dpm-p08.cyf-kr.edu.pl/dpools/p08-fs14/vo.plgrid.pl/2013-10-16/file8f59b952-ef81-4b10-ba60-01226e0b393e.121044910.0, instead a one like gsiftp://dpm-p08.cyf-kr.edu.pl/dpm-p08.cyf-kr.edu.pl:/dpools/p08-fs14/vo.plgrid.pl/2013-10-16/file8f59b952-ef81-4b10-ba60-01226e0b393e.121044910.0 should be passed to it (with the dpm url and ':' added). Is JSaga constructing these url's by itself? - it should usually be obtained from the SRM...
Is JSaga going to support the new version of DPMs? Or does anybody have any workaround?
I would much appreciate any help,
The SRM adaptor is officially maintained so YES if there is a new version of DPM, it will be supported.
I'll have a look asap. I don't think there is any workaround.