You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2013/07/23 10:48:49 UTC
[jira] [Updated] (CAMEL-6443) camel-quickfix - Engine that could
not start (e.g. because of store creation problems) is still stored in the
engiens map, thus making futher starts problematic
[ https://issues.apache.org/jira/browse/CAMEL-6443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen updated CAMEL-6443:
-------------------------------
Fix Version/s: 2.12.0
2.11.2
2.10.7
Summary: camel-quickfix - Engine that could not start (e.g. because of store creation problems) is still stored in the engiens map, thus making futher starts problematic (was: Engine that could not start (e.g. because of store creation problems) is still stored in the engiens map, thus making futher starts problematic)
> camel-quickfix - Engine that could not start (e.g. because of store creation problems) is still stored in the engiens map, thus making futher starts problematic
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-6443
> URL: https://issues.apache.org/jira/browse/CAMEL-6443
> Project: Camel
> Issue Type: Bug
> Components: camel-quickfix
> Affects Versions: 2.10.0
> Reporter: Vitalii Tymchyshyn
> Assignee: Claus Ibsen
> Fix For: 2.10.7, 2.11.2, 2.12.0
>
>
> It's even worse as because of https://issues.apache.org/jira/browse/CAMEL-6441
> if two starts was not successful, engine becomes totally broken.
> The only workaround I can see now is to create new component instance for each endpoint.
--
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