Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: pass (nike.apache.org: domain of bengt.rodehav@gmail.com
 designates 74.125.83.45 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:sender:date:x-google-sender-auth:message-id:subject
         :from:to:content-type;
        b=CnxcFyJZOO9LQYN5a2ZR6VOrqzbFuuxVxTd1gAyt5dOs5El+NtZn8UgvWdLNk8gYL4
         AtSJ0KgB7QQ+HboTeQiIGc8/Aff2fzWhJ8e8DMBepsrC2WhI2PuwgoZ7bTqzqZCLvcsG
         m7d3XJ2+whyRwniVLlsECK/j2zaA+G/6DvaIE=
MIME-Version: 1.0
Sender: bengt.rodehav@gmail.com
Date: Fri, 15 Oct 2010 15:28:37 +0200
Message-ID: <AANLkTi=C9pc8w=urxmvf+BGTZfye_N30sgtuQtM0B1qT@mail.gmail.com>
Subject: camel-quartz and unique timername
From: Bengt Rodehav <bengt@rodehav.com>
To: users@camel.apache.org
Content-Type: multipart/alternative; boundary=001517510fdcd62ad20492a7cd4d

--001517510fdcd62ad20492a7cd4d
Content-Type: text/plain; charset=ISO-8859-1

I'm using camel-quartz (Camel 2.4) and have some problems with the timer
name (part of the URI).

It seems that if I have two different routes (using camel-quartz) with the
same timername, only one of the quartz endpoints will be activated, e g:

from("quartz://mytimername"?cron=0+*+*+*+*+?+*").to(endpoint1)

from("quartz://mytimername"?cron=30+*+*+*+*+?+*").to(endpoint2)


If I make sure that the timernames are unique, both quartz endpoints will
work. Thus I conclude that the timername must be unique (maybe this is a
quartz thing and not a camel-quartz thing).

However, I get no indication that something is wrong since the camel route
is started and looks fine although the quartz endpoint will never trigger.
This is not a good situation. In my case I use this for monitoring purposes.
I thought that the monitoring worked fine but it was actually never
triggered at all.

I'm not sure if this due to camel-quartz or quartz itself. However, if it is
possible for camel-quartz to determine that the endpoint was created OK (not
OK if duplicate timer names), then this should case the camel context to
fail.

I run this in an OSGi environment (Karaf 1.6.0). Thus routes like the above
can be created independent of each other which makes it hard to guarantee
that the timername is unique.

/Bengt

--001517510fdcd62ad20492a7cd4d--