<html>
  <head>
    <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <p>I need to load REST-AT participants from the crash recovery store
      and notify REST-AT coordinator (via REST API) of their URLs. This
      doesn't have to be done on the server start, but until it's done
      REST-AT coordinator recovery will be printing warnings because it
      won't be able to contact participants. So the sooner it's done the
      better, hence my question about a listener which could be invoked
      once the server completed boot-up.</p>
    <p>Gytis<br>
    </p>
    <br>
    <div class="moz-cite-prefix">On 13/12/2016 23:45, Stuart Douglas
      wrote:<br>
    </div>
    <blockquote
cite="mid:CAAoo=c7k=dTLoQAofe_NqzTWUYbJxWNHT4mhxgSgvfdsnJjajg@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div>Why do you need to make a rest call while startup is taking
          place?<br>
          <br>
        </div>
        Stuart<br>
      </div>
      <div class="gmail_extra"><br>
        <div class="gmail_quote">On Wed, Dec 14, 2016 at 9:22 AM, Gytis
          Trikleris <span dir="ltr">&lt;<a moz-do-not-send="true"
              href="mailto:gtrikler@redhat.com" target="_blank">gtrikler@redhat.com</a>&gt;</span>
          wrote:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">Is there a
            way to make sure I'm making the service call not too early?<br>
            <br>
            Also, ControlledProcessStateService methods which are used
            in that<br>
            commit are deprecated. That's why I wasn't sure if it's OK
            for me to use<br>
            them.<br>
            <div class="HOEnZb">
              <div class="h5"><br>
                <br>
                On 13/12/2016 22:34, Brian Stansberry wrote:<br>
                &gt; That commit you linked shows the mechanism for
                getting a notification of process state changes (inject
                ControlledProcessStateService and register a property
                change listener.)<br>
                &gt;<br>
                &gt; But, that commit is opening up the listener when it
                gets the notification, so if you listen for the same
                notification and make a call it’s going to be racy.<br>
                &gt;<br>
                &gt;&gt; On Dec 13, 2016, at 3:26 PM, Gytis Trikleris
                &lt;<a moz-do-not-send="true"
                  href="mailto:gtrikler@redhat.com">gtrikler@redhat.com</a>&gt;
                wrote:<br>
                &gt;&gt;<br>
                &gt;&gt; Hello,<br>
                &gt;&gt;<br>
                &gt;&gt; I'm wondering if there is a way to register a
                listener which would be<br>
                &gt;&gt; invoked when server status has changed. More
                specifically when<br>
                &gt;&gt; application server completed start-up.<br>
                &gt;&gt;<br>
                &gt;&gt; The reason for that is that after [1] commit
                was introduced our rest<br>
                &gt;&gt; transaction tests started to fail. The cause
                seems to be rest service<br>
                &gt;&gt; call during the start of one of our services.
                That call doesn't<br>
                &gt;&gt; necessarily have to be executed during the
                service start. However, the<br>
                &gt;&gt; sooner it's done the better and if it would be
                possible to register some<br>
                &gt;&gt; sort of callback to be invoked once start-up
                was done, that would be great.<br>
                &gt;&gt;<br>
                &gt;&gt; Thanks,<br>
                &gt;&gt;<br>
                &gt;&gt; Gytis<br>
                &gt;&gt;<br>
                &gt;&gt;<br>
                &gt;&gt; [1]<br>
                &gt;&gt; <a moz-do-not-send="true"
href="https://github.com/wildfly/wildfly/commit/d56cd18137d3acbcb5027744d5ce57f3ebc46d8e"
                  rel="noreferrer" target="_blank">https://github.com/wildfly/<wbr>wildfly/commit/<wbr>d56cd18137d3acbcb5027744d5ce57<wbr>f3ebc46d8e</a><br>
                &gt;&gt;<br>
                &gt;&gt; ______________________________<wbr>_________________<br>
                &gt;&gt; wildfly-dev mailing list<br>
                &gt;&gt; <a moz-do-not-send="true"
                  href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a><br>
                &gt;&gt; <a moz-do-not-send="true"
                  href="https://lists.jboss.org/mailman/listinfo/wildfly-dev"
                  rel="noreferrer" target="_blank">https://lists.jboss.org/<wbr>mailman/listinfo/wildfly-dev</a><br>
                <br>
                ______________________________<wbr>_________________<br>
                wildfly-dev mailing list<br>
                <a moz-do-not-send="true"
                  href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a><br>
                <a moz-do-not-send="true"
                  href="https://lists.jboss.org/mailman/listinfo/wildfly-dev"
                  rel="noreferrer" target="_blank">https://lists.jboss.org/<wbr>mailman/listinfo/wildfly-dev</a></div>
            </div>
          </blockquote>
        </div>
        <br>
      </div>
    </blockquote>
    <br>
  </body>
</html>