Bugzilla – Bug 3256
Recoverability fails in WaitingForStateChanges
Last modified: 2005-05-13 11:02:21
You need to
before you can comment on or make changes to this bug.
I'm seeing recoverability problems if the contianer crashes right after a
successful submit but before
any JSM notifications are received. When the container comes back up and the
job is resubscribed to
the JSM, it never recieves any notifications. The globus-fork.log has both an
Active and Done entry for
the job, though.
I added some more logging to confirm that no JSM notifications are occuring
either before or after the container crash. Is the timestamp being updated
before the state change even notification?
I can't seem to reproduce this anymore. I'm going to close it and let it be
reopened if anyone sees it