james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tellier Benoit (JIRA)" <server-...@james.apache.org>
Subject [jira] [Resolved] (JAMES-2448) Camel container is too long to start
Date Thu, 05 Jul 2018 02:41:00 GMT

     [ https://issues.apache.org/jira/browse/JAMES-2448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Tellier Benoit resolved JAMES-2448.
    Resolution: Fixed

[https://github.com/linagora/james-project/pull/1512] solved the issue

> Camel container is too long to start
> ------------------------------------
>                 Key: JAMES-2448
>                 URL: https://issues.apache.org/jira/browse/JAMES-2448
>             Project: James Server
>          Issue Type: Improvement
>          Components: JMAP, SpoolManager &amp; Processors, tests
>            Reporter: Tellier Benoit
>            Assignee: Antoine Duprat
>            Priority: Major
> A classic mailet container takes up to 1 s to load on a warm JVM.
> Fast startup is critical for our testing strategy (relying heavily on integration tests).
We should make camel container loading faster.
> Ideas:
>  - Some parameters are passed to components via dynamically generated properties, on
a per call basis. This is inefficient and can be passed by a constructor.
>  - Many classes used in CamelMailetContainer are not static
>  - We finally can heavily simplify the logic expressed in Camel DSL, and express it through
a *split - process* way, instead of relying on *camel choices*.
> We should measure the effect on boot time, and run Gatling SMTP test to evaluate the
impact on delivery.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org

View raw message