camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vitalii Tymchyshyn (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CAMEL-6443) Engine that could not start (e.g. because of store creation problems) is still stored in the engiens map, thus making futher starts problematic
Date Mon, 10 Jun 2013 11:42:21 GMT

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

Vitalii Tymchyshyn updated CAMEL-6443:
--------------------------------------

          Component/s: camel-quickfix
    Affects Version/s: 2.10.0
    
> 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
>
> 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

Mime
View raw message