#647 Protocol "automatic" for stage-in/out

TBD at some time
closed-wont-fix
UNICORE/X (76)
6.6
5
2013-12-13
2013-07-26
No

The URC supports an "automatic" protocol with the scheme "u6" which is supposed to select the best protocol between two sites. If this is used for stage-in and -out, it leads to an exception "filetransfer uses unsupported protocol". The "u6" scheme is supported for server-server transfers, but not for data staging. This needs to be fixed.
To reproduce, set the preferred protocol in the URC preferences to "automatic" and submit a job which has a stage-in from some UNICORE storage.

Discussion

  • Bjoern Hagemeier

    This seems to apply to client-triggerend transfers in URC, too. Selecting a file in one storage, e.g. job directory and trying to copy/paste it to another storage, will fail with the following exception, even if the client is set to prefer BFT.

    de.fzj.unicore.wsrflite.xmlbeans.BaseFault: Could not initiate send file. Reason: de.fzj.unicore.xnjs.io.UnsupportedProtocolException: Transfer /out_0051.png->U6:https://zam025s02.zam.kfa-juelich.de:7700/VSGC-2/services/StorageManagement?res=default_storage#/bjoernh/unicore_pngs/out_0051.png uses unsupported protocol(s)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
    at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
    at java.lang.reflect.Constructor.newInstance(Constructor.java:532)
    at org.codehaus.xfire.client.ClientFaultConverter.processFaultDetail(ClientFaultConverter.java:57)
    at org.codehaus.xfire.client.ClientFaultConverter.invoke(ClientFaultConverter.java:32)
    at org.codehaus.xfire.handler.HandlerPipeline.invoke(HandlerPipeline.java:131)
    at org.codehaus.xfire.client.Client.onReceive(Client.java:424)
    at org.codehaus.xfire.transport.http.HttpChannel.sendViaClient(HttpChannel.java:139)
    at org.codehaus.xfire.transport.http.HttpChannel.send(HttpChannel.java:48)
    at org.codehaus.xfire.handler.OutMessageSender.invoke(OutMessageSender.java:26)
    at org.codehaus.xfire.handler.HandlerPipeline.invoke(HandlerPipeline.java:131)
    at org.codehaus.xfire.client.Invocation.invoke(Invocation.java:79)
    at org.codehaus.xfire.client.Invocation.invoke(Invocation.java:114)
    at org.codehaus.xfire.client.Client.invoke(Client.java:336)
    at eu.unicore.security.xfireutil.client.ReliableProxy.handleRequest(ReliableProxy.java:122)
    at eu.unicore.security.xfireutil.client.ReliableProxy.doInvoke(ReliableProxy.java:102)
    at eu.unicore.security.xfireutil.client.ReliableProxy.invoke(ReliableProxy.java:69)
    at sun.proxy.$Proxy10.SendFile(Unknown Source)
    at de.fzj.unicore.uas.client.StorageClient.SendFile(StorageClient.java:508)
    at de.fzj.unicore.uas.client.StorageClient.sendFile(StorageClient.java:580)
    at de.fzj.unicore.rcp.servicebrowser.utils.RemoteFileUtils$1.run(RemoteFileUtils.java:314)
    at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)

     
  • Bjoern Hagemeier

    • Affected Versions: --> 6.6
     
  • Bernd Schuller

    Bernd Schuller - 2013-12-13
    • status: open --> closed-wont-fix
    • Fixed in: -->
    • Milestone: UNICORE6.6 --> TBD at some time
     
  • Bernd Schuller

    Bernd Schuller - 2013-12-13

    I'd rather remove this "u6" protocol from the server completely, and find a better way to select the best protocol

     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks