Hi,
Thank you for your reply! I managed to solve the problem by simply upgrading
to the new version of Camel (2.5) which eliminated all of the symptoms
described above.
Regards,
Frankie
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Problem-using-custom-defined-deadlett
The StartStop routes test is probably a good start.
StartAndStopRoutesTest.java - it is in Camel - core.
On Dec 22, 2010, at 4:52 PM, Ivan L wrote:
>
> Hi,
>
> I have several routes defined in the ActiveMQ configuration. I need to be
> able to programmatically change the list the routes - add
Anyone? Is there some kind of config setting on the connections that makes
the connection restart work?
maarten.dirkse wrote:
>
> Sorry, should've included that info in the initial mail. Here's how I've
> setup my connection factories:
>
> class="org.apache.activemq.spring.ActiveMQConnectionF
Hi,
I have several routes defined in the ActiveMQ configuration. I need to be
able to programmatically change the list the routes - add new and delete
existing ones without changing the configuration and restarting the broker.
I suppose I need to get hold of the Camel Context and then modify the
On Dec 17, 2010, at 1:14 PM, Alex Dean wrote:
>
> On Dec 16, 2010, at 5:33 PM, Alex Dean wrote:
>
>>
>> I'll get a useful test written up tomorrow morning, and create a new JIRA
>> issue if Jeff doesn't beat me to it.
>
> I've created https://issues.apache.org/jira/browse/AMQ-3094 for this p
On Dec 22, 2010, at 10:32 AM, stratio wrote:
>
> I added the content header as you told me in my Ruby client and i get a
> strange behaviour...
>
> When i run the Ajax client sometimes it connects and gets the messaged from
> the server correctly (i can see the messages looking at the response)
I added the content header as you told me in my Ruby client and i get a
strange behaviour...
When i run the Ajax client sometimes it connects and gets the messaged from
the server correctly (i can see the messages looking at the response) and
sometimes it doesn't connect and the response looks li
Hi,
try
((TextMessage)message).getText()
but there are better ways to achieve what your code is doing here.
Cheers
--
Dejan Bosanac
-
FuseSource - The experts in open source integration and messaging.
Email: dej...@fusesource.com
Web: http://fusesource.com
Twitter: http://twitt
Hi there, i have constructed an interceptor in order to get producers messages.
the code is below.
public class mypluginBroker extends BrokerFilter {
public void send(ProducerBrokerExchange producer, Message message)
throws Exception {
/*System.out.println("Mes
On Dec 22, 2010, at 3:13 AM, stratio wrote:
> Ok, I just commented the line "headers[ 'Connection' ] = 'close';" and now
> from the admin page i can see my client connecting to the topic and
> consuming the messages
I checked this issue in Chrome, and while I do see the error you reported
("ref
On Dec 22, 2010, at 5:32 AM, stratio wrote:
> Content :
>
>
>
>
>
>
>
>
> So I guess that the reason for which i don't see anything on the browser is
> that the response is a binary message. I saw this
> https://issues.apache.org/jira/browse/AMQ-2833 about this problem
> (considering i'm
I checked the server response and this is what i get :
Headers :
Request
URL:http://localhost:8161/demo/amq?timeout=45000&d=1293017028128&r=0.2588740265928209
Request Method:GET
Status Code:200 OK
Request Headers
Accept:application/xml, text/xml, */*
Accept-Charset:ISO-8859-1,utf-8;q=0.7,*;q=0.3
Ok, I just commented the line "headers[ 'Connection' ] = 'close';" and now
from the admin page i can see my client connecting to the topic and
consuming the messages
Now the only problem left is that these messages aren't showed on the
browser.
This is the code I'm running :
amq.init({ uri: 'am
13 matches
Mail list logo
