Specifically, based on the log, it appears that in dCache a special token
is generated by the refering node that is packaged up with the subsequent
request (this is allowed by the protocol). This token is used to verify
that the same file is being opened that was presented to the refering
node. In dCache 1.9.10 that token is not being passed back to the client.
It would appear that 1.9.5 solves that issue.
On Fri, 24 Sep 2010, Lukasz Janyst wrote:
> On Wed, Sep 22, 2010 at 5:22 PM, Carlos Osuna <[log in to unmask]> wrote:
>> We tested it with a newer version of dCache, 1.9.10 and it works. The
>> problem appears only in our production version of dCache 1.9.5. Of course we
>> also reported to the dCache team, but understanding why xrootd complains may
>> help here.
> If that's the case then I would assume that it is some sort of issue
> of the dCache implementation of the protocol...