Why do you need to make a rest call while startup is taking place?


On Wed, Dec 14, 2016 at 9:22 AM, Gytis Trikleris <gtrikler@redhat.com> wrote:
Is there a way to make sure I'm making the service call not too early?

Also, ControlledProcessStateService methods which are used in that
commit are deprecated. That's why I wasn't sure if it's OK for me to use

On 13/12/2016 22:34, Brian Stansberry wrote:
> That commit you linked shows the mechanism for getting a notification of process state changes (inject ControlledProcessStateService and register a property change listener.)
> 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.
>> On Dec 13, 2016, at 3:26 PM, Gytis Trikleris <gtrikler@redhat.com> wrote:
>> Hello,
>> I'm wondering if there is a way to register a listener which would be
>> invoked when server status has changed. More specifically when
>> application server completed start-up.
>> The reason for that is that after [1] commit was introduced our rest
>> transaction tests started to fail. The cause seems to be rest service
>> call during the start of one of our services. That call doesn't
>> necessarily have to be executed during the service start. However, the
>> sooner it's done the better and if it would be possible to register some
>> sort of callback to be invoked once start-up was done, that would be great.
>> Thanks,
>> Gytis
>> [1]
>> https://github.com/wildfly/wildfly/commit/d56cd18137d3acbcb5027744d5ce57f3ebc46d8e
>> _______________________________________________
>> wildfly-dev mailing list
>> wildfly-dev@lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/wildfly-dev

wildfly-dev mailing list