[CAMEL-5480] QuickFix session logs in before Camel routes are started

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.9.2
• Fix Version/s: 2.9.4, 2.10.2, 2.11.0
• Component/s: camel-quickfix

Environment

Spring 3.1.0

• Estimated Complexity: Moderate
• Assignee: Claus Ibsen
• Reporter: Michael Horwitz
• Created: 31/Jul/12 21:25
• Updated: 31/Aug/12 07:09
• Resolved: 31/Aug/12 07:09

Description

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.