Re: Camel generating message with correlationid=null and tmp-queue null

relevant to this thread specifically. Tim On Sun, Apr 1, 2018 at 9:19 PM, Tim Bain <tb...@alumni.duke.edu> wrote: -- Forwarded message -- > From: <mallara...@gmail.com> > Date: Thu, Mar 29, 2018 at 5:44 PM > Subject: Re: Camel generating message with correlationid

Re: Camel generating message with correlationid=null and tmp-queue null

Rajesh, First, I want to let you know that although it's possible to edit/delete mailing list posts on the Nabble site after you've posted them, the edits are not sent out to the mailing list via email, so anyone (like me) who works primarily from email will not see the changes you make. So the

Re: Camel generating message with correlationid=null and tmp-queue null

Thank you Tim for this IOException, we have not observed any reasonable exceptions on broker [ producer ] side. attached thread dump jstack.out. Can you please look into and help. -- Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html

Re: Camel generating message with correlationid=null and tmp-queue null

it seems blockingQueue is not actually ACTiveMQDestination, just it is java, so any other suggestions ? at that state we are not able to connect to cloud broker , on client side we are getting : Caused by: java.io.EOFException at java.io.DataInputStream.readInt(Unknown Source)[:1.8.0_60]

Re: Camel generating message with correlationid=null and tmp-queue null

thank you Tim, >>Caused by: java.io.IOException: Failed to perform GET on: https://URL >>Reason: null >>at org.apache.activemq.util.IOExceptionSupport.create(IOExceptionSupport.java:33)[120:org.apache.activemq.activemq-osgi:5.12.3] >>at

Re: Camel generating message with correlationid=null and tmp-queue null

On Sun, Mar 18, 2018 at 9:14 AM, Rajesh Malla wrote: > We have to use https only, because our server broker sits in cloud & > onpremises in another location. via some other url authenticating. this > scenario is working properly in <5.8.0 > of activemq however not

Re: Camel generating message with correlationid=null and tmp-queue null

>Is your client using a failover transport? If so, it's the failover >transport that's re-establishing the connection. we are not using any failover transport I see you're using the https transport. Does it work if you connect with the tcp transport instead? It's possible that there's some

Re: Camel generating message with correlationid=null and tmp-queue null

On Tue, Mar 13, 2018 at 6:52 PM, Rajesh Malla wrote: > when we are looking into Server broker, it has many temperary queues around > more than 2000. So we have removed one network peer. > A->B > B->A > now, after some hours tmp-queues are around 2 digits only. we have

Re: Camel generating message with correlationid=null and tmp-queue null

when we are looking into Server broker, it has many temperary queues around more than 2000. So we have removed one network peer. A->B B->A now, after some hours tmp-queues are around 2 digits only. we have applied below patch : https://issues.apache.org/jira/browse/AMQ-6262 still after some hours

Re: Camel generating message with correlationid=null and tmp-queue null

Was that error happening when you first saw the behavior you first asked about? Are you saying that these are related, or that they're two unrelated issues? I can't see anything obvious about this exception that I would expect to result in the behavior you saw in your first post, so my starting

Re: Camel generating message with correlationid=null and tmp-queue null

following error messages we are seeing on client side : 2018-03-08 18:38:24,248 41319597 [Camel (jcsCoreCamelContext) thread #12 - JmsConsumer[uniquequename]] (org.apache.activemq.activemq-osgi:org.apache.activemq.jms.pool.PooledSession:126) WARN - Caught exception trying close() when putting

Re: Camel generating message with correlationid=null and tmp-queue null

I'll start with the bad news. From what you've written, it could be either product (Camel or ActiveMQ) that's causing the problem, and the people that support the two products are both likely to initially assume it's the other product's doing. So one of the best things you can do is to figure out

Re: Camel generating message with correlationid=null and tmp-queue null

we are using activemq : 5.12.3 apache camel : 2.16.2 -- Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html