Mailing-List: contact issues-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Date: Mon, 17 Jun 2013 07:58:19 +0000 (UTC)
From: "Thomas  (JIRA)" <jira@apache.org>
To: issues@camel.apache.org
Message-ID: <JIRA.12653149.1371455787993.124264.1371455899978@arcas>
In-Reply-To: <JIRA.12653149.1371455787993@arcas>
References: <JIRA.12653149.1371455787993@arcas>
Subject: [jira] [Created] (CAMEL-6462) Question: Clustered environment for
 Camel with quartz and servlet
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Thomas  created CAMEL-6462:
------------------------------

             Summary: Question: Clustered environment for Camel with quartz and servlet
                 Key: CAMEL-6462
                 URL: https://issues.apache.org/jira/browse/CAMEL-6462
             Project: Camel
          Issue Type: Wish
            Reporter: Thomas 


We need to run camel inside a clustered environment (JBoss 7.x or Wildfly EAP 6.x) with some major challenges:
* there are many cron triggered routes using quartz, which should work load balanced (means: a route should work on one note this time and on the other node next time. A job inside a route should not be clustered)
* some servlet endpoints, which need be be called load balanced
* route manipulation through user interaction during runtime
* 2 nodes for failover and work balancing

My approach:
Quartz can be clustered, this should be no problem, isnt' it?
For distributed work on both nodes camel context should be active an both nodes with working routes. In this way servlet endpints should be active and accessible on both nodes, aren't they? 
For modifying camel context through GUI (web) I would write a singleton bean which has access to HA-JNDI and iterate over all (in this case two) camel contexts. 

Would this approach work? Do I miss some point? Exists other approaches betting fitting to this problem?

Thank you for your help. 


--
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