camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CAMEL-5480) QuickFix session logs in before Camel routes are started
Date Fri, 31 Aug 2012 07:10:07 GMT

    [ https://issues.apache.org/jira/browse/CAMEL-5480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13445733#comment-13445733
] 

Claus Ibsen commented on CAMEL-5480:
------------------------------------

Thanks for spotting this.

I adjusted the patch, to check the status on camel context, then there is no need for that
boolean flag.

Ad 2)
Yeah if you can provided a little example then raise it on @dev or a new JIRA and we can take
a look.
                
> QuickFix session logs in before Camel routes are started
> --------------------------------------------------------
>
>                 Key: CAMEL-5480
>                 URL: https://issues.apache.org/jira/browse/CAMEL-5480
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-quickfix
>    Affects Versions: 2.9.2
>         Environment: Spring 3.1.0
>            Reporter: Michael Horwitz
>            Assignee: Claus Ibsen
>            Priority: Minor
>             Fix For: 2.9.4, 2.11.0, 2.10.2
>
>         Attachments: camel_quickfix_startup_patch.patch
>
>
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message