Re: Supporting LDAP HA client

[Yudhi Karunia Surtan <yu...@apache.org>]

Dear fortress Commiters,


Please postpone the release related to the HA LDAP connection pool.
For the round robin strategy, I found a mistake where the request has been
balanced to the given nodes, but after killing one of ldap somehow my logic
failed.

I think I need to again looks how manage the closed connection works on it.

Also for the perf test, round robin strategy give more response time than
previous single connection.

On Wed, Apr 25, 2018, 20:18 Yudhi Karunia Surtan <yu...@apache.org> wrote:

> Hi shawn,
>
> Ok. Will do the internal release using different repository and change the
> pom file at my local repository and once fortress done with released, I
> will again upgrade my IAM into the release version from community.
>
> Thanks and soon will give you the report for the perf test result once it
> is done.
>
>
> On Wed, Apr 25, 2018, 19:52 Shawn McKinney <sm...@apache.org> wrote:
>
>>
>> > On Apr 24, 2018, at 11:50 PM, Yudhi Karunia Surtan <yu...@apache.org>
>> wrote:
>> >
>> > I just commit a new code and test with 2 ldap with round robin
>> connection
>> > strategy.
>> > Bellow are the scenarios:
>> >
>> > - start commander with 2 ldap and shut and start one to another.
>> > - start commander with 1 ldap and start other ldap defined at the
>> > configuration.
>> >
>> > and the result are great both scenarios working well without disturbing
>> the
>> > user interactions, so the HA working smooth.
>>
>> Hey Yudhi, that’s good news.
>>
>> >
>> > On Apr 24, 2018, at 11:50 PM, Yudhi Karunia Surtan <yu...@apache.org>
>> wrote:
>> >
>> > I would like to release this version internally and deploy along with
>> CAS
>> > at my production at Mei 15 and before that i would like to do some
>> > performance test to make sure the logic able to perform in production
>> later.
>> >
>> > Do we have a plan for releasing new fortress version before Mei 15?
>> > If it is yes then i will not using my own version and follow the main
>> > community release line and do the perf test on that version.
>>
>> Sounds like a good plan. This is good timing actually as I was just
>> getting ready to announce plans for a new release - 2.0.1.  We can hold off
>> until May 15.  Keep us apprised on how it goes.
>>
>> Shawn
>>
>>