camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <>
Subject [jira] [Updated] (CAMEL-5480) QuickFix session logs in before Camel routes are started
Date Mon, 13 Aug 2012 11:01:38 GMT


Claus Ibsen updated CAMEL-5480:

         Priority: Minor  (was: Major)
    Fix Version/s: 2.11.0
       Issue Type: Improvement  (was: Bug)
> QuickFix session logs in before Camel routes are started
> --------------------------------------------------------
>                 Key: CAMEL-5480
>                 URL:
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-quickfix
>    Affects Versions: 2.9.2
>         Environment: Spring 3.1.0
>            Reporter: Michael Horwitz
>            Priority: Minor
>             Fix For: 2.11.0
> To recreate the issue:
> 1) Configure the Camel context to have autostart=false
> 2) Create a route that processes the loggin message
> 3) Refresh the Spring application context
> 4) Start the Spring application context
> The QuickFixj engine will be created and started at step 3 but the route that processes
the login message only gets started at step 4. If there are other components in the Spring
application context that are slow to initialize then the QuickFixj engines will login before
the Camel context (and hence the routes) have been started.
> This is an issue for us as we add a username and password to the login message using
a Camel route.
> Proposed solution:
> Have the Dispatcher in the QuickFixjEngine extend ApplicationExtended and disable login
until the CamelContext is started.
> Patch and test to follow. 

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message