[prev in list] [next in list] [prev in thread] [next in thread]
List: forgerock-openidm
Subject: Re: [OpenIDM] Recon threads
From: Robert Jackson <rjackson () nulli ! com>
Date: 2015-02-04 17:37:00
Message-ID: CANLLvL5U6bpWyGtVhbFOK+JATHLM7+UkxZ8n1UpS942m=qw0GA () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Thanks guys. This was my assumption as well.
-Rob
On Wed, Feb 4, 2015 at 9:28 AM, Brendan Miller <brendan.miller@forgerock.com
> wrote:
>
> Matthias is correct--the second change (the implicit triggered sync) is
> executed in the same thread as the event that changed the managed
> object, whether it be a recon or a REST request to create, update,
> delete, etc.
>
> Brendan
>
> On Wed, Feb 04, 2015 at 07:56:21AM +0100, Matthias Tristl wrote:
> > Honestly, I do not know the answer, but the mechanism is this:
> >
> > The secondary change is not a recon, but a single user sync, triggered by
> > the create/update of the managed object (I guess that is the situation
> you
> > are talking about).
> >
> > I assume that the triggered sync is executed in the same thread as the
> > event that changed the managed object, or a new thread would be created.
> >
> > In both cases the number of threads configured for the first recon (and
> > only reconciliation process involved, as the secondary syncs are not part
> > of a new reconciliation) is what counts.
> >
> > Matthias
> >
> >
> >
> > Matthias Tristl : ForgeRock INC
> > e: matthias.tristl@forgerock.com
> > t: +47 47707662
> > w: forgerock.com
> >
> > On Tue, Feb 3, 2015 at 5:08 PM, Robert Jackson <rjackson@nulli.com>
> wrote:
> >
> > > I have a recon threading question. If a recon from a target to a
> source
> > > causes an automatic sync to a second target, which recon's
> 'taskThreads'
> > > setting is effective, the first one, the second one, or a combination
> of
> > > the 2?
> > >
> > > -Rob
> > >
> > > --
> > >
> > > *HI IM |* *Robert Jackson* <rjackson@nulli.com>
> > >
> > > *Identity Architect*
> > >
> > > *Nulli =* *Identity Solution Architects*
> > > *#401, 1228 Kensington Road NW**, Calgary, AB T2N 3P7*
> > > * 403.648.0909 nulli.com <http://www.nulli.com/>*
> > >
> > >
> > > _______________________________________________
> > > OpenIDM mailing list
> > > OpenIDM@forgerock.org
> > > https://lists.forgerock.org/mailman/listinfo/openidm
> > >
> > >
>
> > _______________________________________________
> > OpenIDM mailing list
> > OpenIDM@forgerock.org
> > https://lists.forgerock.org/mailman/listinfo/openidm
>
> _______________________________________________
> OpenIDM mailing list
> OpenIDM@forgerock.org
> https://lists.forgerock.org/mailman/listinfo/openidm
>
--
*HI IM |* *Robert Jackson* <rjackson@nulli.com>
*Identity Architect*
*Nulli =* *Identity Solution Architects*
*#401, 1228 Kensington Road NW**, Calgary, AB T2N 3P7*
* 403.648.0909 nulli.com <http://www.nulli.com/>*
[Attachment #5 (text/html)]
<div dir="ltr">Thanks guys. This was my assumption as \
well.<div><br></div><div>-Rob</div></div><div class="gmail_extra"><br><div \
class="gmail_quote">On Wed, Feb 4, 2015 at 9:28 AM, Brendan Miller <span \
dir="ltr"><<a href="mailto:brendan.miller@forgerock.com" \
target="_blank">brendan.miller@forgerock.com</a>></span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><br> Matthias is correct--the second change (the implicit \
triggered sync) is<br> <span class="">executed in the same thread as the event that \
changed the managed<br> </span>object, whether it be a recon or a REST request to \
create, update,<br> delete, etc.<br>
<br>
Brendan<br>
<span class=""><br>
On Wed, Feb 04, 2015 at 07:56:21AM +0100, Matthias Tristl wrote:<br>
> Honestly, I do not know the answer, but the mechanism is this:<br>
><br>
> The secondary change is not a recon, but a single user sync, triggered by<br>
> the create/update of the managed object (I guess that is the situation you<br>
> are talking about).<br>
><br>
> I assume that the triggered sync is executed in the same thread as the<br>
> event that changed the managed object, or a new thread would be created.<br>
><br>
> In both cases the number of threads configured for the first recon (and<br>
> only reconciliation process involved, as the secondary syncs are not part<br>
> of a new reconciliation) is what counts.<br>
><br>
> Matthias<br>
><br>
><br>
><br>
> Matthias Tristl : ForgeRock INC<br>
> e: <a href="mailto:matthias.tristl@forgerock.com">matthias.tristl@forgerock.com</a><br>
> t: <a href="tel:%2B47%2047707662" value="+4747707662">+47 47707662</a><br>
> w: <a href="http://forgerock.com" target="_blank">forgerock.com</a><br>
><br>
> On Tue, Feb 3, 2015 at 5:08 PM, Robert Jackson <<a \
href="mailto:rjackson@nulli.com">rjackson@nulli.com</a>> wrote:<br> ><br>
> > I have a recon threading question. If a recon from a target to a \
source<br> > > causes an automatic sync to a second target, which recon's \
'taskThreads'<br> > > setting is effective, the first one, the second \
one, or a combination of<br> > > the 2?<br>
> ><br>
> > -Rob<br>
> ><br>
> > --<br>
> ><br>
</span>> > *HI IM |* *Robert Jackson* <<a \
href="mailto:rjackson@nulli.com">rjackson@nulli.com</a>><br> > ><br>
> > *Identity Architect*<br>
> ><br>
> > *Nulli =* *Identity Solution Architects*<br>
> > *#401, 1228 Kensington Road NW**, Calgary, AB T2N 3P7*<br>
> > * <a href="tel:403.648.0909" value="+14036480909">403.648.0909</a> \
<a href="http://nulli.com" target="_blank">nulli.com</a> <<a \
href="http://www.nulli.com/" target="_blank">http://www.nulli.com/</a>>*<br> <div \
class="HOEnZb"><div class="h5">> ><br> > ><br>
> > _______________________________________________<br>
> > OpenIDM mailing list<br>
> > <a href="mailto:OpenIDM@forgerock.org">OpenIDM@forgerock.org</a><br>
> > <a href="https://lists.forgerock.org/mailman/listinfo/openidm" \
target="_blank">https://lists.forgerock.org/mailman/listinfo/openidm</a><br> > \
><br> > ><br>
<br>
> _______________________________________________<br>
> OpenIDM mailing list<br>
> <a href="mailto:OpenIDM@forgerock.org">OpenIDM@forgerock.org</a><br>
> <a href="https://lists.forgerock.org/mailman/listinfo/openidm" \
target="_blank">https://lists.forgerock.org/mailman/listinfo/openidm</a><br> <br>
_______________________________________________<br>
OpenIDM mailing list<br>
<a href="mailto:OpenIDM@forgerock.org">OpenIDM@forgerock.org</a><br>
<a href="https://lists.forgerock.org/mailman/listinfo/openidm" \
target="_blank">https://lists.forgerock.org/mailman/listinfo/openidm</a><br> \
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div \
class="gmail_signature"><div dir="ltr"><p></p><p></p><p><b><span \
style="font-size:10.0pt;font-family:Arial;color:#4e4e4e">HI IM |</span></b><b><span \
style="font-size:10.0pt;font-family:Arial;color:#888888"> </span></b><span \
style="font-size:10.0pt;font-family:"Lucida Grande";color:#888888"><a \
href="mailto:rjackson@nulli.com" target="_blank"><b><span \
style="font-family:Arial;color:#808e1d">Robert Jackson</span></b></a></span></p>
<p style="margin-bottom:12.0pt"><b><span \
style="font-size:7.5pt;font-family:Arial;color:#4d4d4d">Identity \
Architect</span></b><b><span \
style="font-size:10.0pt;font-family:Arial;color:#888888"></span></b></p>
<p><b><span style="font-size:7.5pt;font-family:Arial;color:#808e1d">Nulli \
=</span></b><span><b><span style="font-size:7.5pt;font-family:Arial;color:#330033"> \
</span></b></span><b><span \
style="font-size:7.5pt;font-family:Arial;color:#4d4d4d">Identity Solution \
Architects</span></b><b><span \
style="font-size:10.0pt;font-family:Arial;color:#888888"></span></b></p>
<b><span style="font-size:7.5pt;font-family:Arial;color:#4d4d4d">#401,
1228 Kensington Road NW</span></b><b><span \
style="font-size:7.5pt;font-family:Arial;color:#4d4d4d">, Calgary, AB T2N \
3P7</span></b><b><span style="font-size:7.5pt;font-family:Arial;color:#4d4d4d"><br> \
<a value="+14036480917">403.648.0909</a> <span> </span><a \
href="http://www.nulli.com/" \
target="_blank">nulli.com</a></span></b><p></p><p></p></div></div> </div>
_______________________________________________
OpenIDM mailing list
OpenIDM@forgerock.org
https://lists.forgerock.org/mailman/listinfo/openidm
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic