[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
20040929: ldm 6.1 - change in "-m" behavior
- Subject: 20040929: ldm 6.1 - change in "-m" behavior
- Date: Wed, 13 Oct 2004 14:33:09 -0600
Harry,
>Date: Wed, 13 Oct 2004 10:33:34 -0700
>From: Harry Edmon <address@hidden>
>Organization: University of Washington
>To: Steve Emmerson <address@hidden>
>Subject: Re: 20040929: ldm 6.1 - change in "-m" behavior
>Keywords: 200409282351.i8SNpxHP002118 LDM 6.1
The above message contained the following:
> Okay - I finally ran the experiment. Here is the log file:
...
The relevant logfile entries are the following:
> Oct 13 17:28:27 freshair rpc.ldmd[28241]: Starting Up (version: 6.1.0; built:
> Sep 17 2004 13:51:28)
> Oct 13 17:28:27 freshair thelma[28258]: Starting Up(6.1.0): thelma.ucar.edu:
> TS_ZERO TS_ENDT {{NNEXRAD|NIMAGE|DIFAX|FNEXRAD|FSL2|WMO, ".*"}}
> Oct 13 17:28:28 freshair thelma[28258]: Delay: 0.0690 sec
> Oct 13 17:28:28 freshair thelma[28258]: pq_sequence():
> time(insert)-time(create): 0.0438 s
> Oct 13 17:28:28 freshair thelma[28258]: lastmatch:
> dd0475134717e62043d2328e075e9bd7 11 20041013172828.158 ANY 000
> -TESTPQACT
> Oct 13 17:28:28 freshair thelma[28258]: Desired product class:
> 20041013172828.158 TS_ENDT {{NNEXRAD|NIMAGE|DIFAX|FNEXRAD|FSL2|WMO, ".*"}}
> Oct 13 17:28:28 freshair thelma[28258]: Connected to upstream LDM-6
The above indicates that the downstream LDM that was going to request
data of type
NNEXRAD|NIMAGE|DIFAX|FNEXRAD|FSL2|WMO ".*"
from Thelma discovered that a matching data-product existed in the
product-queue. The feedtype of that data-product was ANY and the
insertion-time was 20041013172828.158. Therefore, that was the
beginning-time that the downstream LDM used in its request.
The feedtype of any given data-product should be as restrictive as
possible to avoid problems like this.
Where are you getting data-products with a feedtype of ANY?
Regards,
Steve Emmerson