Bug 6141 - Getting the service hosts in DelegatedCredentialDestroyHelper is ambiguous
: Getting the service hosts in DelegatedCredentialDestroyHelper is ambiguous
Status: RESOLVED FIXED
: GRAM
wsrf managed execution job service
: alpha
: Macintosh All
: P3 normal
: 4.2
Assigned To:
:
:
:
:
  Show dependency treegraph
 
Reported: 2008-06-09 12:06 by
Modified: 2008-06-09 12:16 (History)


Attachments


Note

You need to log in before you can comment on or make changes to this bug.


Description From 2008-06-09 12:06:07
To identify whether a credential resource can be destroyed locally or via a
WS call, ServiceHost.getHost() and ServiceHost.getPort() is compared to the
host and port of the address of the EPR of the delegated credential.
However, ServiceHost.getHost() returns an IP or a hostname, depending on
whether a MessageContext is associated with the executing thread.
So in some situations a WS call is done to destroy a transfer credential, even
if RFT (and the credential) is located in the same container.

Solution:
ServiceHost.getDefaultHost() does a better job.