aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (Jira)" <>
Subject [jira] [Commented] (ARIES-1929) Performance optimization
Date Wed, 11 Sep 2019 13:16:00 GMT


ASF subversion and git services commented on ARIES-1929:

Commit 0816520e651c2ba7172720463a118753859b9a00 in aries-jax-rs-whiteboard's branch refs/heads/master
from Carlos Sierra
[;h=0816520 ]

[ARIES-1929] Special error handling in the first rewire

If we get a wiring error in the first (probably bulk) rewire we need to
discard one by one the possible services that are causing it. Since CXF
does not inform about which service is causing the error we need to try
incrementally. Once we have ruled out the failing services we mark them
as such in the runtime and in the extension registry, which might cause
some more extensions or services to be unregistered from the
application (even the very application).

During this process we disable the registrator so we don't get
re-entrant rewires and, when finalized, we try to wire the application
again. If the application still fails we mark it as failing.

> Performance optimization
> ------------------------
>                 Key: ARIES-1929
>                 URL:
>             Project: Aries
>          Issue Type: Improvement
>          Components: jax-rs-whiteboard
>    Affects Versions: jax-rs-whiteboard-1.0.4
>            Reporter: Carlos Sierra
>            Priority: Major
>             Fix For: jax-rs-whiteboard-1.0.5
> Currently the deployment of one application involves a redeployment of the whole application
per service that conforms the application. That means that, if an application is composed
of 20 services it will be rewired 20 times even if all the services are present when the application
is registered.
> This should not be necessary and an optimization can be made for the _best case_, being
that all the services are present at the moment of the application registration so one rewire
should be made.

This message was sent by Atlassian Jira

View raw message