IBM Directory server changelog connector - question.

Hi - we're porting code over from 5.2 to 6.1.1 With 6.1.1 (we're not on 
any of the FixPacks yet) I have noticed unusual bahaviour with one of 
our IDS changelog connectors. In the AL, the iteration stops and then 
finishes within milliseconds - it is not waiting for the "timeout" of
10 
seconds.
However, within the same AL, if I set aside the old changelog connector 
and create a new changelog connector with the same parameters on the 
GUI, I can get it to behave as expected.

Thanks Eddie - I will open up a PMR in the next hour or two. I have now 
seen this happen in two of our environments.

Eddie Hartman wrote:
> Hi, Derryck,
> 
> Definitely sounds like something you should speak with
> support about.
> 
> Also, if you take a look at the Config xml itself, searching
> until you find your changelog Connector (under the <AssemblyLine>
> node which will sort under <Folders name="AssemblyLines">)
> you will probably see some differences in the parameter settings.
> Bring these along (5.2 and 6.1.1 converted Configs) when you
> contact our L2 wizards.
> 
> It could also be that all you really need is fp2
>
http://www-1.ibm.com/support/docview.wss?rs=697&context=SSCQGF&dc=D400&a
mp;uid=swg24017390&loc=en_US&cs=UTF-8&lang=en 
> 
> 
> -Eddie
> 
> Derryck Lamptey wrote:
> 
>> Hi - we're porting code over from 5.2 to 6.1.1 With 6.1.1 (we're not 
>> on any of the FixPacks yet) I have noticed unusual bahaviour with one 
>> of our IDS changelog connectors. In the AL, the iteration stops and 
>> then finishes within milliseconds - it is not waiting for the 
>> "timeout" of 10 seconds.
>> However, within the same AL, if I set aside the old changelog 
>> connector and create a new changelog connector with the same 
>> parameters on the GUI, I can get it to behave as expected.
>>

Hi, Derryck,

Definitely sounds like something you should speak with
support about.

Also, if you take a look at the Config xml itself, searching
until you find your changelog Connector (under the <AssemblyLine>
node which will sort under <Folders name="AssemblyLines">)
you will probably see some differences in the parameter settings.
Bring these along (5.2 and 6.1.1 converted Configs) when you
contact our L2 wizards.

It could also be that all you really need is fp2
http://www-1.ibm.com/support/docview.wss?rs=697&context=SSCQGF&dc=D400&a
mp;uid=swg24017390&loc=en_US&cs=UTF-8&lang=en

-Eddie

Derryck Lamptey wrote:
> Hi - we're porting code over from 5.2 to 6.1.1 With 6.1.1 (we're not on 
> any of the FixPacks yet) I have noticed unusual bahaviour with one of 
> our IDS changelog connectors. In the AL, the iteration stops and then 
> finishes within milliseconds - it is not waiting for the
"timeout" of 10 
> seconds.
> However, within the same AL, if I set aside the old changelog connector 
> and create a new changelog connector with the same parameters on the 
> GUI, I can get it to behave as expected.
> 

Nearly at closeout on this. We opened up a PMR, and finally pinpointed 
the issue as being related to the new behaviour of (interplay between) 
the Timeout/Sleep parameter. A level 2 (Brian) pointed us to a technote 
called "TDS Changelog connector Timeout and Sleep Interval behavior 
change" which explains the situation.

http://www-1.ibm.com/support/docview.wss?rs=697&context=SSCQGF&dc=DB520&
amp;dc=DB560&uid=swg21270924&loc=en_US&cs=UTF-8&lang=en&rss=
ct697tivoli

epilogue: We are retrofitting all our code with the timeout value being 
more than the sleep value on all our changelog-dependent iterators, in 
all our environments.
epi-epilogue: one of the puzzling aspects of this issue was that in one 
of our environments, ITDI 6.1.1 (no FP) was working fine even though the 
sleep/timeout values could be expected to not work (according to the 
note). In our other two environments, the same timeout values did not 
work, and had to be fixed according to the technote.

Derryck Lamptey wrote:
> Thanks Eddie - I will open up a PMR in the next hour or two. I have now 
> seen this happen in two of our environments.
> 
> Eddie Hartman wrote:
>> Hi, Derryck,
>>
>> Definitely sounds like something you should speak with
>> support about.
>>
>> Also, if you take a look at the Config xml itself, searching
>> until you find your changelog Connector (under the
<AssemblyLine>
>> node which will sort under <Folders
name="AssemblyLines">)
>> you will probably see some differences in the parameter settings.
>> Bring these along (5.2 and 6.1.1 converted Configs) when you
>> contact our L2 wizards.
>>
>> It could also be that all you really need is fp2
>>
http://www-1.ibm.com/support/docview.wss?rs=697&context=SSCQGF&dc=D400&a
mp;uid=swg24017390&loc=en_US&cs=UTF-8&lang=en 
>>
>>
>> -Eddie
>>
>> Derryck Lamptey wrote:
>>
>>> Hi - we're porting code over from 5.2 to 6.1.1 With 6.1.1 (we're
not 
>>> on any of the FixPacks yet) I have noticed unusual bahaviour with
one 
>>> of our IDS changelog connectors. In the AL, the iteration stops and

>>> then finishes within milliseconds - it is not waiting for the 
>>> "timeout" of 10 seconds.
>>> However, within the same AL, if I set aside the old changelog 
>>> connector and create a new changelog connector with the same 
>>> parameters on the GUI, I can get it to behave as expected.
>>>