Bug 3256 – Recoverability fails in WaitingForStateChanges

Bug 3256 - Recoverability fails in WaitingForStateChanges

Summary:

Recoverability fails in WaitingForStateChanges

Status:	RESOLVED

Product:	GRAM
Component:	wsrf managed execution job service
Version:	development
Platform:	Macintosh All

Importance:	P3 normal
Target Milestone:	4.0.1
Assigned To:	Peter Lane

URL:
Keywords:

Depends on:
Blocks:	3348
	Show dependency tree / graph

Reported:	2005-05-02 16:58 by Peter Lane
Modified:	2005-05-13 11:02 (History)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note

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

Description From Peter Lane 2005-05-02 16:58:05

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.

------- Comment #1 From Peter Lane 2005-05-02 18:31:57 -------

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?

------- Comment #2 From Peter Lane 2005-05-11 14:44:48 -------

I can't seem to reproduce this anymore.  I'm going to close it and let it be
reopened if anyone sees it 
again.