thank you very very much - that transaction config works with the route.
And thank you for the test code which I now intend to study. Hopefully
I'll produce a blog post useful to others.
cheers,
Alistair
---
Alistair Young
Senior Software Engineer
UHI@Sabhal Mòr O
FWIW it was down to using bean id='activemq' for ActiveMQComponent.
Calling it anything else solved the problem. There's an
org.apache.camel.management.DefaultManagementAgent MBean created
name="activemq" so I wonder if they were clashing.
Alistair
--------
tes but not
with the filter/simple in the route.
any help would be appreciated.
thanks,
Alistair
---
Alistair Young
Senior Software Engineer
UHI@Sabhal Mòr Ostaig
>>> "Alistair Young" 25/07/12 12:59 PM >>>
I've been following the Camel in
y for standalone Camel use and only use one when it's
running inside ActiveMQ?
thanks,
Alistair
---
Alistair Young
Senior Software Engineer
UHI@Sabhal Mòr Ostaig
es through the header checking route and it worked
too. So it seems down to my incomprehension of transactions and why
there were both ActiveMQConnectionFactory and ActiveMQComponent defined.
thanks for listening though.
Alistair
---
Alistair Young
Senior Software Engineer
UHI@
t;activemq:topic:topicB"
route
send 10 message, between 3 and 4 disappear and never reach topicB. No
errors logged.
Alistair
---
Alistair Young
Senior Software Engineer
UHI@Sabhal Mòr Ostaig
>>> "Alistair Young" 25/07/12 9:52 AM >>>
I have a ro
t get the route to take more than one message. Non
transacted routes. I have an errorHandlerRef but it's never called. The
route just stops.
thanks,
Alistair
---
Alistair Young
Senior Software Engineer
UHI@Sabhal Mòr Ostaig
the jar required the java mail jar to be in the classpath - doh! all
working now.
Alistair
---
Alistair Young
Senior Software Engineer
UHI@Sabhal Mòr Ostaig
>>> Willem Jiang 24/07/12 3:27 PM >>>
What's the stack trace did you get ?
On Tue Jul 24 21:16:
Is there any reason a org.apache.camel.Processor cannot call a static
method in a class that is in a jar in ACTIVEMQ_HOME/lib? The processor
just blows up whenever it tries to call the static method.
thanks,
Alistair
---
Alistair Young
Senior Software Engineer
UHI@Sabhal Mòr
it possible to use a
processor inside choice/when?
thanks,
Alistair
-------
Alistair Young
Senior Software Engineer
UHI@Sabhal Mòr Ostaig
> Isn't it difficult to do proper error handling with the EIP
> based approach?
I wouldn't think so. In fact it's probably easier than writing lots of specific
error handling code. I'm using Invalid Message Channel (IMS) to handle some
errors. Anything that fails goes in the IMC via a route that
, Alistair Young wrote:
> why would adding this:
>
>
>
> to this:
>
> org.apache.activemq.camel.component.ActiveMQComponent
>
> cause the broker to stop working? There are no transacted routes. The faster
> the messages come in, the more disappear. I have a very simpl
is transacted.
Is there anything special the client has to do? Surely not though, as there are
no transacted routes.
Alistair
--
mov eax,1
mov ebx,0
int 80h
On 2 Oct 2011, at 09:43, Alistair Young wrote:
> eventually found the problem.
>
> if transactions are enabled nothing wo
x27;m not sure how to go about fixing it. Would you have any pointers please?
thanks,
Alistair
--
mov eax,1
mov ebx,0
int 80
On 30 Sep 2011, at 13:35, Alistair Young wrote:
> thanks T
arch.maven.org
>
>
>
> From: Christian Schneider [ch...@die-schneider.net]
> Sent: Friday, September 30, 2011 4:49 AM
> To: users@camel.apache.org
> Subject: Re: 2.8.1 source?
>
> Am 30.09.2011 12:11, schrieb Alistair Young:
>> none of the 2.8.1 source link
d the same with an embedded activemq instance and it
> works great.
> Maybe this has to do with broker settings? I can setup a tiny test project
> for you if you want to try that?
>
> On Fri, Sep 30, 2011 at 11:27 AM, Alistair Young
> wrote:
>
>> I can now reproduce this e
none of the 2.8.1 source link work. Where can I get it please?
thanks,
Alistair
--
mov eax,1
mov ebx,0
int 80h
empty and there
are no errors anywhere.
Alistair
--
mov eax,1
mov ebx,0
int 80h
On 30 Sep 2011, at 09:12, Alistair Young wrote:
> getting somewhere.
>
>
>
>
>
>
>
>
> - producer clock is 2mins ahead of broker clock, timestamp
ing to the activemq topic instead, all messages get through no
matter how fast they come.
Alistair
--
mov eax,1
mov ebx,0
int 80h
On 29 Sep 2011, at 18:10, Alistair Young wrote:
> no connection pool. What was disturbing was the first message sent to the
> broker after a restart and clean
ny prefetch limits or
> anything like that.
> Are you using a connection pool?
>
> On Thu, Sep 29, 2011 at 5:05 PM, Alistair Young
> wrote:
>
>> I think this way madness lies.
>>
>> 17 sent to topicA, dispatchCount = 15, dequeueCount = 12
>> topicB enqueu
earth?
Alistair
--
mov eax,1
mov ebx,0
int 80
On 29 Sep 2011, at 15:41, Alistair Young wrote:
> nup - cleaned out the data dir and restarted the broker. First message in
> vanished. Wasn't persisted. So something is fundamentally broken.
>
> topicA inflightCoun
sn't routed and just
vanished from the broker.
Alistair
--
mov eax,1
mov ebx,0
int 80
On 29 Sep 2011, at 15:13, Alistair Young wrote:
> route goes from topicA -> topicB, transacted.
> topicA inflightCount = 96 and increases on each batch of incoming messages
> top
e on activemq for the queue or topic in question
> and see how many were enqueued vs dispatched.
> Check your deadletter queue from there too
>
> On Thu, Sep 29, 2011 at 12:52 PM, Alistair Young
> wrote:
>
>> dunno - nothing works. Random messages are just vanishing once
on message : 1317291897071 = 29 Sep 2011 10:24:57 GMT, presumably the
timestampplugin doing this
message vanishes
but all messages display this clock behaviour and not all vanish.
Alistair
--
mov eax,1
mov ebx,0
int 80
On 29 Sep 2011, at 10:24, Alistair Young wrote:
> just saw yo
just saw your info about transacted being before from - will change that and
monitor again.
thanks,
Alistair
--
mov eax,1
mov ebx,0
int 80
On 29 Sep 2011, at 10:18, Alistair Young wrote:
> just noticed a batch of identical 5 messages, three were missing and another
>
,
password = *, brokerPath = null, brokerMasterConnector = false, manageable
= true, clientMaster = true, faultTolerant = false}
Alistair
--
mov eax,1
mov ebx,0
int 80
On 29 Sep 2011, at 09:36, Alistair Young wrote:
>> Should be after
> it is after from - do you mean
uld be after
>
>
> On Thu, Sep 29, 2011 at 10:09 AM, Alistair Young
> wrote:
>>> Do you use message expiry?
>> no
>>
>>> timestamp plugin
>>
>> using that
>>
>> activemq 5.5.0
>> camel 2.8.0
>> spring 3.0.5
>>
>&g
gging[1] and camel logging FAQ[2]
>>
>> [1]http://camel.apache.org/how-do-i-enable-debug-logging.html
>> [2]http://camel.apache.org/logging-questions.html
>>
>> Taariq
>>
>>
>> On Wed, Sep 28, 2011 at 1:23 PM, Alistair Young
>> wrote:
>>
;
> I suggest enable tracing to see exactly what happens in your route.
>
> regards, Marco
>
> Am 28.09.2011 13:01, schrieb Alistair Young:
>> I now have a dead letter channel which is empty after losing 9 out of 10
>> messages. I also added a logging handler which logged n
I now have a dead letter channel which is empty after losing 9 out of 10
messages. I also added a logging handler which logged nothing. Verified the
messages arrived at the broker, then they just vanished.
Alistair
--
mov eax,1
mov ebx,0
int 80h
On 28 Sep 2011, at 11:42, Alistair Young
.com
> Blog: http://www.baselogic.com/blog/
> Linked IN: http://linkedin.com/in/mickknutson
> Twitter: http://twitter.com/mickknutson
> ---
>
>
>
> On Wed, Sep 28, 2011 at 6:16 AM, Alistair Young
> wrote:
>
>> Hi there,
>>
>> is there anything
/
> Linked IN: http://linkedin.com/in/mickknutson
> Twitter: http://twitter.com/mickknutson
> ---
>
>
>
> On Wed, Sep 28, 2011 at 6:16 AM, Alistair Young
> wrote:
>
>> Hi there,
>>
>> is there anything that would cause camel to ignore messages in a
Hi there,
is there anything that would cause camel to ignore messages in a route? I'm
getting persistent messages simply disappearing from a transacted route. I've
verified the messages arrive at the activemq broker (tcpdump) and also that on
one occasion, 5 out of 6 of the messages just disapp
FWIW, I need to get at messages in a Processor using XMLBeans so I used it to
compile the message schema to a jar and use that instead of working with the
raw XML.
Alistair
--
mov eax,1
mov ebx,0
int 80
On 3 Aug 2011, at 07:11, Claus Ibsen wrote:
> Hi
>
> On Tue, Aug 2, 2011 at 6
I'd like to look at the 2.8.0 source to see if there's an example of sending
email from a spring defined route but all the source links are 404
Alistair
--
mov eax,1
mov ebx,0
int 80h
FWIW this is what I did for a transactional route to stop messages disappearing
from the original queue if the broker went down:
http://activemq.apache.org/schema/core";
id="matrixBrokerID"
brokerName="matrixBroke
tp://camel.apache.org/bean
>
> Try something like this
>
>
>
>
> On Thu, Jul 7, 2011 at 11:43 AM, Alistair Young
> wrote:
>> sorry if I'm fuddling about too much. Perhaps if I rephrase:
>>
&g
testuserCreatePayload);
}
the Processor has the default path "/tmp/test/"
Alistair
--
mov eax,1
mov ebx,0
int 80h
On 6 Jul 2011, at 19:00, Claus Ibsen wrote:
> On Mon, Jul 4, 2011 at 3:55 PM, Alistair Young
> wrote:
>> Camel seems to load its own instances of beans
eax,1
mov ebx,0
int 80h
On 5 Jul 2011, at 22:43, Christian Müller wrote:
> Why not using the PropertyPlaceholder mechanism and providing a config file
> for test? That's the way we handle properties which changes from one
> environment to another.
> Am 04.07.2011 15:56 schrieb &
------
mov eax,1
mov ebx,0
int 80
On 5 Jul 2011, at 02:38, Willem Jiang wrote:
> On Mon Jul 4 20:38:48 2011, Alistair Young wrote:
>> found the prob - there was an activemq/ca
thanks Ashwin
Alistair
--
mov eax,1
mov ebx,0
int 80
On 4 Jul 2011, at 20:47, Ashwin Karpe wrote:
> Hi,
>
> It is possible to do via the Registry.
>
> You can store a bean reference in the registry and then refer to it. A
> aimple way to do this is to use the "Ref" component.
>
Camel seems to load its own instances of beans in camel-config.xml
testProcessor = (TestProcessor)ctx.getBean("testProcessor");
testProcessor.setPath("/home/test");
but when i do this:
sendBody("activemq:topic:edirectoryprocessed", testuserCreatePayload);
testProcessor has its old path. i.e. te
found the prob - there was an activemq/camel instance already running. An error
would have been nice...
--
mov eax,1
mov ebx,0
int 80h
On 4 Jul 2011, at 13:18, Alistair Young wrote:
> hello camel list,
>
> when testing a camel-config.xml the following never returns from ct
returns. Am I doing
something wrong?
thanks,
Alistair
----
Alistair Young
Senior Software Engineer
UHI@Sabhal Mòr Ostaig
thanks Ashwin, all working now.
cheers,
Alistair
--
mov eax,1
mov ebx,0
int 80h
On 23 Jun 2011, at 20:03, Ashwin Karpe wrote:
> Hi,
>
> There are several things here
>
>a> Are the subscribers truly durable ?
>In order to set up a durable subscription on a JMS endpoint, you
>
> mov eax,1
> mov ebx,0
> int 80h
>
>
>
>
> On 23 Jun 2011, at 12:00, Alistair Young wrote:
>
>> If I declare a route:
>>
>>
>>
>>
>> when I restart tomcat, the activemq:topic:src is still there as it has
>> persistent messa
forgot to add transacted to the route:
but I just get the error:
Invalid content was found starting with element 'transacted'. One of ...
expected
Alistair
--
mov eax,1
mov ebx,0
int 80h
On 23 Jun 2011, at 12:00, Alistair Young wrote:
> If I de
If I declare a route:
when I restart tomcat, the activemq:topic:src is still there as it has
persistent messages but the activemq:topic:dest topic disappears along with all
messages waiting for durable subscribers in it.
Camel takes all the messages from dest and puts them in src, and they
thanks Ashwin
Alistair
--
mov eax,1
mov ebx,0
int 80h
On 31 May 2011, at 14:03, Ashwin Karpe wrote:
> Hi,
>
> You will need to make your consumers transactional so that messages are
> restored back on the Topic if the route fails to process the message due to
> shutdown, failures etc.
>
I have a bit of a problem where persistent messages are lost when Camel routes
are used. If I send a persistent message to an ActiveMQ topic and read it using
a durable topic subscriber, the messages survive a server restart if the
subscriber hasn't read them.
If I route those persistent message
50 matches
Mail list logo