- **status**: review -- fixed
- **Comment**:
opensaf-4.4.x:
changeset: 6199:30807c19453f
branch: opensaf-4.4.x
tag: tip
parent: 6193:5e0774313f6d
user:Hung Nguyen hung.d.ngu...@dektech.com.au
date:Wed Dec 03 18:04:55 2014 +0700
summary: immsv: Correct the
- **status**: unassigned -- review
- **assigned_to**: Hung Nguyen
---
** [tickets:#953] immsv :the jobDuration condition should be corrected**
**Status:** review
**Milestone:** 4.4.2
**Created:** Tue Jul 08, 2014 03:43 AM UTC by A V Mahesh (AVM)
**Last Updated:** Tue Oct 07, 2014 08:12 AM UTC
- **Milestone**: 4.3.3 -- 4.4.2
---
** [tickets:#953] immsv :the jobDuration condition should be corrected**
**Status:** unassigned
**Milestone:** 4.4.2
**Created:** Tue Jul 08, 2014 03:43 AM UTC by A V Mahesh (AVM)
**Last Updated:** Wed Jul 09, 2014 09:58 AM UTC
**Owner:** nobody
On
- **Milestone**: 4.5.FC -- 4.3.3
---
** [tickets:#953] immsv :the jobDuration condition should be corrected**
**Status:** unassigned
**Milestone:** 4.3.3
**Created:** Tue Jul 08, 2014 03:43 AM UTC by A V Mahesh (AVM)
**Last Updated:** Tue Jul 08, 2014 03:47 AM UTC
**Owner:** nobody
On
- **Comment**:
On 6/25/2014 9:56 PM, Anders Björnerstedt wrote:
You are correct.
I guess I was just never expecting anyone to contemplate seting MAX_WAIT to as
high a value as 50+ seconds. But that could very well be the case for some
deployments.
So this can be seen as a defect. The
