On Tue, Jun 23, 2009 at 5:39 PM, buzzterrier wrote:
>
> Hello,
>
> We have an existing ActiveMQ service running on a dedicated server. I am
> having trouble figuring out how to integrate my Camel service with the
> existing ActiveMQ service. Do we have to now start the ActiveMQ service
> using th
On Tue, Jun 23, 2009 at 2:12 PM, RuneB wrote:
>
> Ok. See CAMEL-1749.
>
Thanks I had a look into it and added my comments to the ticket.
>
> - Rune
>
>
>
>
> Claus Ibsen-2 wrote:
> >
> > On Mon, Jun 22, 2009 at 12:10 PM, RuneB wrote:
> >
> >>
> >> No, it's not the JAXB unmarshaller that thro
On Tue, Jun 23, 2009 at 10:25 AM, akuhtz wrote:
>
> Hi,
>
> I'm trying to configure redelivery in the loadbalancer but I don't get the
> expected result.
>
> What I want to do is something like this:
>
> > loadbalancer +> route A (with maximumRedelivery=2)
> | +---
Hi
I have created a ticket to track the bug
https://issues.apache.org/activemq/browse/CAMEL-1755
And I have a fix ready that I will commit shortly.
Could you test the trunk again?
On Wed, Jun 24, 2009 at 12:58 PM, Claus Ibsen wrote:
>
>
> On Tue, Jun 23, 2009 at 10:25 AM, akuhtz wrote:
>
>>
>
Hi Claus,
Works fine now =) Thanks for the fix.
--
View this message in context:
http://www.nabble.com/Redelivery-in-Loadbalancer-tp24161904p24184289.html
Sent from the Camel - Users mailing list archive at Nabble.com.
On Wed, Jun 24, 2009 at 2:58 PM, akuhtz wrote:
>
> Hi Claus,
>
> Works fine now =) Thanks for the fix.
Great you really is fast to test. I assume you build the code since you got
hold of the .jar so quickly :)
BTW if you good requirements or ideas to improve the failover loadbalancer
we have a
Hi all,
I've stumbled upon an issue and am not sure how to solve it. :confused:
Basicly I've setup some routes using camel 1.6.0 that consume messages and
dispatches them to our services. Everything works fine except for one
thing.
When I restart my camel context I start to lose messages, and I
Here's the complete exception
org.springframework.jms.InvalidDestinationException: Cannot publish to a
deleted Destination: temp-queue://ID:56P3J-57576-1245848023626-0:0:2; nested
exception is javax.jms.InvalidDestinationException: Cannot publish to a
deleted Destination: temp-queue://ID:56P3J-57
Here is the stack trace:
[java] [ultMessageListenerContainer-15] EndpointMessageListener
DEBUG Endpoint[activemq:queue:bluid:programs] consumer receiving JMS
message: ActiveMQObjectMessage {commandId = 8, responseRequired = true,
messageId = ID:xw-014-2157-1245858065483-0:0:2:1:1,
Hi
Thanks. We did some work on the trunk with that type converter thingy. But
let me take a look at it tomorrow. I have started this thread.
I will build an unit test in camel-jms that will send your SearchTerm class
over jms.
To prepare for tomorrow can you post what can help, eg snippets of your
Sorry, stupid user trick.
I had the camel context's package tag too narrow on my client. I had had it
looking only at my foo.bar.bluidapi.jms package to use my ServerRoutes impl.
But my pojo was in foo.bar.bluidapi.shared.
When I changed the camel:package to foo.bar.bluidapi it worked.
I just stumbled into an issue where using an @Consume annotation on a bean
ended up creating 2 consumers when that bean was deployed in an OSGi bundle
containing 2 camel contexts.
It appears 1 consumer is created for each @Consume annotation for each
context, even if the endpoint the @Consume ref
On Wed, Jun 24, 2009 at 8:50 PM, ariekenb wrote:
>
> I just stumbled into an issue where using an @Consume annotation on a bean
> ended up creating 2 consumers when that bean was deployed in an OSGi bundle
> containing 2 camel contexts.
>
> It appears 1 consumer is created for each @Consume annota
Hi
Stopping / shutting down is hard. We have debated this before and would in
the future look into how we can make it better.
Are you having AMQ embedded with Camel that you stop, or is AMQ a remote
broker?
On Wed, Jun 24, 2009 at 3:56 PM, Tim83 wrote:
>
> Here's the complete exception
>
> o
14 matches
Mail list logo
