Bug 5012 - Container in livelock state for an incorrectly mapped DN
: Container in livelock state for an incorrectly mapped DN
Status: RESOLVED WONTFIX
: GRAM
wsrf managed execution job service
: 4.0.3
: PC Linux
: P3 normal
: ---
Assigned To:
:
:
:
:
  Show dependency treegraph
 
Reported: 2007-02-15 15:41 by
Modified: 2012-09-05 11:43 (History)


Attachments


Note

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


Description From 2007-02-15 15:41:46
The globus container gets into a livelock state if the requesting DN is mapped
to a user that isn't in the passwords file for the situations when the
credentials are delegated from the client. If the credential isn't delegated,
it works fine.

We have noted this problem with 'globusrun-ws' command with -J option. Without
the -J option, the container appropriately returns an error. The exact command
used was:  globusrun-ws -submit -streaming  -J -F
https://<host-name>:8443/wsrf/services/ManagedJobFactoryService -job-command
/bin/hostname

This problem has been noted both in 4.0.1 and 4.0.3 versions and on 32 bit and
64 bit systems.

Apologies if this isn't a bug.

Thanks,
Abhishek.
------- Comment #1 From 2007-02-26 13:50:33 -------
Hi,
Any updates on this ?
------- Comment #2 From 2007-08-07 10:08:28 -------
I'm assuming this is a GRAM issue that occurs when the service attempts to
write the delegated credential to the user's job directory, so I'll reassign to
the GRAM team.
------- Comment #3 From 2012-09-05 11:43:35 -------
Doing some bugzilla cleanup...  Resolving old GRAM3 and GRAM4 issues that are
no longer relevant since we've moved on to GRAM5.  Also, we're now tracking
issue in jira.  Any new issues should be added here:

http://jira.globus.org/secure/VersionBoard.jspa?selectedProjectId=10363