Re: Camel JMS consumer with dynamic selector to read ActiveMQ DLQueues

2025-03-11 Thread Ephemeris Lappis
Hello. Original messages globally (we already have some kind of messages that use it) must not have a time to live. And I found no way to tell ActiveMQ to add a time to live when a message is moved to a DLQ by a rollback of the recipient process :I don't think we have to change the transaction han

RE: Camel JMS consumer with dynamic selector to read ActiveMQ DLQueues

2025-03-11 Thread Mattern, Alex
If you are just looking to trash old messages then use the timeToLive setting when producing messages on the DLQ. https://camel.apache.org/components/4.10.x/eips/message-expiration.html If you want a manually triggered process, then you can create a consumer application that consumes X number of

Re: Camel JMS headers

2024-09-16 Thread Claus Ibsen
On Mon, Sep 16, 2024 at 5:30 PM Chirag wrote: > Thanks Claus. > > Balint, fix is on a new branch and not on 4.0.x. Would you know how to > cherrypick to 4.0.x branch to get it in version you need and validate? > > Camel 4.0.x is EOL and not supported. > > On Mon, Sep 16, 2024 at 4:55 AM Bálint

Re: Camel JMS headers

2024-09-16 Thread Chirag
Thanks Claus. Balint, fix is on a new branch and not on 4.0.x. Would you know how to cherrypick to 4.0.x branch to get it in version you need and validate? On Mon, Sep 16, 2024 at 4:55 AM Bálint Baráth wrote: > Thanks for the quick response, and the fix! > > Claus Ibsen ezt írta (időpont: 202

Re: Camel JMS headers

2024-09-16 Thread Bálint Baráth
Thanks for the quick response, and the fix! Claus Ibsen ezt írta (időpont: 2024. szept. 14., Szo 11:31): > Hi > > Yeah lets investigate this I created a ticket > https://issues.apache.org/jira/browse/CAMEL-21219 > > On Thu, Sep 12, 2024 at 8:36 AM Bálint Baráth > wrote: > > > Hello! > > > > I'm

Re: Camel JMS headers

2024-09-14 Thread Claus Ibsen
Hi Yeah lets investigate this I created a ticket https://issues.apache.org/jira/browse/CAMEL-21219 On Thu, Sep 12, 2024 at 8:36 AM Bálint Baráth wrote: > Hello! > > I'm using camel 4.0.6 with java 17 and springboot 3.2.6. > When using camel with JMS and using a request-reply EIP, camel puts som

Re: Camel JMS headers

2024-09-14 Thread Bálint Baráth
Yes, the property gets added as 'CamelJmsDeliveryMode' and has a value of 1 or 2. But the usual JMSDeliveryMode with persistent/nonpersistent is also there, added by the camels JmsConfiguration class. I saw a comment in the code, that this property is temporary, and it removes it, when setting the

Re: Camel JMS headers

2024-09-13 Thread Chirag
Is Tibco seeing it as DeliveryMode or with Camel name on it? Do you also see DeliveryMode? regards, On Thu, Sep 12, 2024 at 10:13 AM Bálint Baráth wrote: > Hello! > > FYI if somebody runs into the same problem: > I managed to create a workaround, after finding where the header gets > added. I

Re: Camel JMS headers

2024-09-12 Thread Bálint Baráth
Hello! FYI if somebody runs into the same problem: I managed to create a workaround, after finding where the header gets added. It's inside the tibco jms implementation, where all the properties on the message get added as jms headers, so the CamelJmsDeliveryMode int property was added. I created

Re: Camel JMS component / Dynamic destination on consumer

2024-04-17 Thread Ephemeris Lappis
Hello Claus. Indeed, this is a perfect way to get the dynamic queue name : {{sys:XXX}}. Thanks a lot ! Regards. Le mer. 17 avr. 2024 à 17:04, Claus Ibsen a écrit : > > Hi > > You can use {{ }} syntax that can refer to JVM sys properties also. > > The toD example you have is using simple langua

Re: Camel JMS component / Dynamic destination on consumer

2024-04-17 Thread Claus Ibsen
Hi You can use {{ }} syntax that can refer to JVM sys properties also. The toD example you have is using simple language and its not the same as {{ }} but they can both use sys/env variables etc. On Wed, Apr 17, 2024 at 4:36 PM Ephemeris Lappis wrote: > Hello. > > I'm looking for some way to

Re: Camel JMS & transaction : redelivery conditions ignored

2024-03-12 Thread Ephemeris Lappis
Hello.Claus ! Well ! after more tests, I can confirm that on the broker side all works as expected. I've also found some way to set set the route such a way that failing messages are moved to the DLQ the same way they are when processed by applications.

Re: Camel JMS & transaction : redelivery conditions ignored

2024-03-11 Thread Ephemeris Lappis
Hello Claus. I'm not sure that I should change anything on the broker side : with the same ActiveMQ, java applications with a similar connection factory configuration (maximumRedeliveries=0) actually do a rollback on failing messages processing, and the broker moves them to DLQ queues. These appli

Re: Camel JMS & transaction : redelivery conditions ignored

2024-03-11 Thread Claus Ibsen
Hi You need to set this on the broker side, it's the one that does the redelivery. Every broker has their own settings for DLQ and redelivery. On Mon, Mar 11, 2024 at 2:20 PM Ephemeris Lappis wrote: > Hello. > > It seems that the JMS consumer ignores the redelivery conditions that > I set on my

Re: Camel JMS headers not updated by producer

2024-01-17 Thread Ephemeris Lappis
done : https://issues.apache.org/jira/browse/CAMEL-20338 Le mer. 17 janv. 2024 à 08:03, Claus Ibsen a écrit : > > Hi > > No this is not possible out of the box with dynamic queue names. > > It may be desirable to enrich the message with > a CamelJmsDestinationNameProduced header that includes the

Re: Camel JMS headers not updated by producer

2024-01-16 Thread Claus Ibsen
Hi No this is not possible out of the box with dynamic queue names. It may be desirable to enrich the message with a CamelJmsDestinationNameProduced header that includes the name. You are welcome to create a JIRA. On Mon, Jan 8, 2024 at 10:05 AM Ephemeris Lappis wrote: > Hello. > > If it's

Re: Camel JMS headers not updated by producer

2024-01-08 Thread Ephemeris Lappis
Hello. If it's confirmed, it means that I can't retrieve the actual resulting queue the message is sent to ? I'd need to retrieve it in some event notifiers, out of the Camel routes code, that spies all the exchanges, the same way I do for generated files retrieving the header "CamelFileNameProduc

Re: Camel JMS headers not updated by producer

2024-01-07 Thread Jeremy Ross
I think Camel only sets those headers when a JMS message is received. https://camel.apache.org/components/4.0.x/jms-component.html#_message_format_when_receiving On Thu, Jan 4, 2024 at 5:56 AM Ephemeris Lappis wrote: > Hello. > > I've observed that some JMS headers are not updated after a messa

Re: Camel JMS / Set message time to live

2023-04-03 Thread Ephemeris Lappis
Hello again ! The code I've given before, setting the header "JMSExpiration" with a computed date ("now+30m", it seems that Camel takes the timestamp's long value, and not the date string, to set the sent message header) works if and only if I add "preserveMessageQos=true" to the endpoint's URI. T

Re: Camel JMS / Set message time to live

2023-04-03 Thread ski n
I think setting "JMSExpiration" from a header isn't supported. Only these four: CamelJMSDestinationName (producer) CamelJmsRequestTimeout (producer) JMSCorrelationID (producer) JMSReplyTo (producer) Don't know why, but other ones have no effect. The component does some message mapping though

Re: Camel JMS / Set message time to live

2023-04-03 Thread Ephemeris Lappis
No, I can't : we work on a Red-Hat Fuse cluster, and the brokers and the related configured components are provided by the cluster (in groups including Karaf instances), and are shared for all our business bundles and their queues. We'd want to set time to live (expiration) only for some queues, no

Re: Camel JMS / Set message time to live

2023-04-03 Thread ski n
Can you set the parameter globally like this: ActiveMQComponent activeMQComponent = new ActiveMQComponent(); activeMQComponent.setPreserveMessageQos(true); context.addComponent("activemq2",activeMQComponent); On Mon, Apr 3, 2023 at 12:27 PM Ephemeris Lappis wrote: > Hello. > > In fact I think

Re: Camel JMS / Set message time to live

2023-04-03 Thread Ephemeris Lappis
Hello. In fact I think I'd only need to set one header for expiration time. Something like that : ${date:now+30m} But it seems that for overriding the default JMSExpiration another change must be done on the endpoint (otherwise the JMSExpira

Re: Camel JMS / Set message time to live

2023-04-03 Thread ski n
I should be possible as Camel Headers are translated to JMS Headers when sending to an ActiveMQ queue or topic. This can be tricky though as sometimes JMS Headers are not set by the client but by the broker (for example JMSTimestamp), so you can't use all headers. You can check this page with the

Re: Camel JMS / Set message time to live

2023-04-02 Thread Ephemeris Lappis
Hello. Thanks for your idea. I had a look at the JMs component unit tests, but I've not found any that use only headers to set messages time to live. Could you please give us some example ? Thanks again. Regards Le ven. 31 mars 2023 à 18:34, Claus Ibsen a écrit : > > A good idea is to look at t

Re: Camel JMS / Set message time to live

2023-03-31 Thread Claus Ibsen
A good idea is to look at the unit tests in the camel components On Fri, Mar 31, 2023 at 6:27 PM Ephemeris Lappis wrote: > Hello. > > I've not found any way to set messages time to live when sending to a > JMS (activemq) queue. > > I'd like to set headers only, without changing the endpoint URI.

RE: camel-jms long receiveTimeout preventing shutdown with Oracle AQ

2021-10-15 Thread Mattern, Alex
- From: Mattern, Alex Sent: Thursday, October 7, 2021 3:00 PM To: users@camel.apache.org Subject: [EXTERNAL SENDER:] RE: camel-jms long receiveTimeout preventing shutdown with Oracle AQ Claus Isben, The reason for wanting a long receive timeout is to prevent the queue server from having

RE: camel-jms long receiveTimeout preventing shutdown with Oracle AQ

2021-10-07 Thread Mattern, Alex
Mattern -Original Message- From: Claus Ibsen Sent: Thursday, October 7, 2021 10:24 AM To: users@camel.apache.org Subject: [EXTERNAL SENDER:] Re: camel-jms long receiveTimeout preventing shutdown with Oracle AQ Hi Do NOT use such a long receive timeout, that is not its purpose. The

Re: camel-jms long receiveTimeout preventing shutdown with Oracle AQ

2021-10-07 Thread Claus Ibsen
Hi Do NOT use such a long receive timeout, that is not its purpose. The timeout should be a reasonable value that allows camel-jms (eg spring jms) to react on shutdown or stopping, or reducing concurrent consumers if there are no more pending messages. On Thu, Oct 7, 2021 at 3:05 PM Mattern, Alex

Re: Camel JMS transferExchange=true Exception

2018-01-15 Thread Claus Ibsen
Hi Its an Apache ActiveMQ setting (not Camel specific) that do not allow java serialized objects by default, and you need to configure it with the approved classes/packages. If you want to help improve the docs at Apache Camel, then you can submit a PR with doc updates on this file https://github

Re: Camel JMS Logging question

2017-12-19 Thread Claus Ibsen
Hi I think you can configure a custom errorHandler on the JMS endpoint / component and there you can log only what you want. See details at https://github.com/apache/camel/blob/master/components/camel-jms/src/main/docs/jms-component.adoc On Tue, Dec 19, 2017 at 6:54 PM, Кристина Солдатко wrote:

Re: camel-jms

2016-12-01 Thread sa_james
See this link for how my problem was solved. BAsically, use /main.run()/ instead of /main.start()/ -- View this message in context: http://camel.465427.n5.nabble.com/camel-jms-tp5790832p5790898.html Sent from the Camel - U

Re: camel-jms

2016-12-01 Thread sa_james
Funnily enough, when I swap the activeMQConnectionFactory with websphereConnectionFactory, spring does the reconnect. I might be missing something. -- View this message in context: http://camel.465427.n5.nabble.com/camel-jms-tp5790832p5790895.html Sent from the Camel - Users mailing list archiv

Re: camel-jms

2016-12-01 Thread sa_james
Id did the testing with Spring trying to reconnect to a Websphere and I did configured the factory as follows: Sadly it does not reconnect. What I am missing? Thanks. -- View this message in context: http://camel.465427.n5.nabble.com/camel-jms-tp5790832p5790875.

Re: camel-jms

2016-12-01 Thread Claus Ibsen
JMS connection pool configurations may have failover / reconnect logic. As well as JMS clients may have vendor specific features for this, such as ActiveMQ with the failover url. Other vendors have likely something similar. Its not in the JMS spec and thus not a general way of configuring and setti

Re: camel-jms

2016-11-30 Thread sa_james
I did not know that. I will test it. Thanks. -- View this message in context: http://camel.465427.n5.nabble.com/camel-jms-tp5790832p5790844.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: camel-jms

2016-11-30 Thread Quinn Stevenson
You’re not missing anything - that’s the way the camel-jms and camel-sjms components work. They get a connection from the connection factory when they startup, and the keep using it. You can configure the Camel route to handle some JMS Exceptions and sometimes get the reconnect to work that wa

Re: camel-jms

2016-11-30 Thread sa_james
What u describe is failover. What I mean is for the client to wait until a machine that went down, comes back up while the client is looping waiting to reconnect. camel-sjms does not even let you know that the connection has been lost. Camel just silently continues to run while the connection is go

Re: camel-jms

2016-11-30 Thread Quinn Stevenson
If you’re using ActiveMQ, use a failover URL ( http://activemq.apache.org/how-do-i-configure-automatic-reconnection.html ) and both camel-jms and camel-sjms will reconnect. > On Nov 30, 2016, at 11:38 AM, sa_james wro

Re: Camel JMS Properties.

2016-09-19 Thread chandler
FYI: if your camel header is named "camel.is.great" then the JMS property will be named "camel_DOT_is_DOT_great" -- View this message in context: http://camel.465427.n5.nabble.com/Camel-JMS-Properties-tp5787616p5787736.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Camel JMS Properties.

2016-09-15 Thread Minh Tran
Hi You’re getting confused between JMS properties and Camel properties. They are two different concepts which happen to have the same name. If you set the camel message header before you publish the JMS message, it will automatically add that header as a JMS property with the same name. I would

Re: camel jms: setting specific MQ headers

2016-09-09 Thread sobha
Hi, We are struggling to put a JMS header for MessageID so that the downstream application can access it as MQMD header. The downstream application is expecting this. Pls help -- View this message in context: http://camel.465427.n5.nabble.com/camel-jms-setting-specific-MQ-headers-tp5722102p

Re: Camel jms - Custom Message ID

2016-05-19 Thread Timothy Bish
On 05/19/2016 09:24 AM, Quinn Stevenson wrote: The JMS Message ID is generated by the JMS server (not Camel) - at least that’s what I remember from the JMS Specs. If there is a was to customize the JMS Message ID, I think you’d have to look at your JMS provider and see what they offer. That i

Re: Camel jms - Custom Message ID

2016-05-19 Thread Quinn Stevenson
The JMS Message ID is generated by the JMS server (not Camel) - at least that’s what I remember from the JMS Specs. If there is a was to customize the JMS Message ID, I think you’d have to look at your JMS provider and see what they offer. > On May 19, 2016, at 4:07 AM, Adarsh_GU wrote: > > H

Re: Camel jms - In Out Pattern

2016-05-19 Thread Adarsh_GU
The issue was while using *inout pattern with this mockresponse route* to poll mock response to response quee. Now I tried with polling some response to response queue first, then i removed above route . In this case request response is wor

Re: Camel jms - In Out Pattern

2016-05-18 Thread Quinn Stevenson
It looks like the other system isn’t setting the JMSCorrelationID, so the route is timing-out waiting for a response with that correlation ID. Have you tried setting replyToType=Exclusive? You can see the details in the camel-jms docs (http://camel.apache.org/jms.html

RE: Camel jms Request reply -scenario with separate queues for request and response

2016-05-18 Thread Steve Huston
> I have 2 queues provided by third party provider 1.request queue, 2.reply > queue > > using camel jms i will send request to request queue, so third party provider > will push respective response to response queue. Ok. > I would to make these calls synchronous. so for each request send to > r

Re: Camel jms - In Out Pattern

2016-05-18 Thread Adarsh_GU
The third party provider will give response only in their response quee, thats why i set replyTo as their response queue name.(instead of temp queue), >From queue console i have observed that while configuring request response basically i have 2 queues from third party.one for sending request an

Re: Camel jms - In Out Pattern

2016-05-18 Thread Henryk Konsek
Hi, You don't have to send message to the response queue. Camel will create a temporary response queue for you: from("jms:foo").setBody().constant("myresponse"); ... String response = producerTemplate.requestBody("jms:foo", "body", String.class); assertThat(response).isEqualTo("myresponse

Re: camel-jms asyncStartListener Issue

2016-04-01 Thread frouxel
yogu13 wrote > ok .. i got the code working, i was mistaken to think there was a timeout > happening, but actually there wasnt.. > > All is good now.. > > Thank you! > > Regards, > -Yogesh Dear Yogesh, I am facing same behavior, with Camel (2.12.4) JMS Endpoint and Websphere (8.5.5.5) MQ conne

Re: Camel JMS, what is a "task" in maxMessagesPerTask?

2016-03-27 Thread David Karlsen
-Original Message- > From: raffi [mailto:raffi.onj...@gmail.com] > Sent: Sunday, March 27, 2016 10:49 AM > To: users@camel.apache.org > Subject: Re: Camel JMS, what is a "task" in maxMessagesPerTask? > > Ahh, ok, thanks Claus. > > > > -- > View th

RE: Camel JMS, what is a "task" in maxMessagesPerTask?

2016-03-27 Thread Vanshul . Chawla
: Re: Camel JMS, what is a "task" in maxMessagesPerTask? Ahh, ok, thanks Claus. -- View this message in context: http://camel.465427.n5.nabble.com/Camel-JMS-what-is-a-task-in-maxMessagesPerTask-tp5779819p5779822.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Camel JMS, what is a "task" in maxMessagesPerTask?

2016-03-27 Thread raffi
Ahh, ok, thanks Claus. -- View this message in context: http://camel.465427.n5.nabble.com/Camel-JMS-what-is-a-task-in-maxMessagesPerTask-tp5779819p5779822.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Camel JMS, what is a "task" in maxMessagesPerTask?

2016-03-27 Thread Claus Ibsen
Its a spring jms option, so you can find more details what it mean at spring jms you can google for spring jms maxMessagesPerTask and find it in their docs somewhere On Sun, Mar 27, 2016 at 4:51 PM, raffi wrote: > While not explicitly mentioned in Camel JMS docs, I'm assuming "task" is a > thr

Re: Camel-JMS JMS Selector getting overridden by new requests

2015-12-08 Thread Claus Ibsen
Yes if the endpoint uri is the same, then its cached in camel. On Tue, Dec 8, 2015 at 6:21 PM, ravi.4indra wrote: > are the endpoints shared between multiple threads even if the bean is of > protoype scope? > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Camel-JMS-

Re: Camel-JMS JMS Selector getting overridden by new requests

2015-12-08 Thread ravi.4indra
are the endpoints shared between multiple threads even if the bean is of protoype scope? -- View this message in context: http://camel.465427.n5.nabble.com/Camel-JMS-JMS-Selector-getting-overridden-by-new-requests-tp5774806p5774838.html Sent from the Camel - Users mailing list archive at Nabble

Re: Camel-JMS JMS Selector getting overridden by new requests

2015-12-07 Thread Claus Ibsen
No you would need to create the endpoint in the code instead of injecting as that is a shared endpoint (its uri is the same). On Mon, Dec 7, 2015 at 11:51 PM, ravi.4indra wrote: > Hi > > We are having a issue where our Selector mesageid is being overidden by the > messageid from new requests. I

Re: Camel JMS Issue

2015-11-06 Thread james.seb7
Hi Claus, As you suggested , I have increased connection time from 2 sec .Now I'm getting more in the logs like below: Nov 06, 2015 2:10:26 PM org.springframework.jms.listener.DefaultMessageListenerContainer handleListenerSetupFailure INFO: JMS message listener invoker needs to establish shared

Re: Camel JMS Issue

2015-11-06 Thread Claus Ibsen
And you only run the app for 2 seconds. You may want to give it more time to startup and connect to tibco. As camel-jms is using spring jms, so you can also search the internet how to use tibco with spring jms as it would be the same configuration needed on the connection factory etc. On Fri, Nov

Re: Camel JMS Issue

2015-11-06 Thread Christian Schneider
Can you show how you configure the connection factory? Christian On 06.11.2015 11:16, james.seb7 wrote: Hi , I'm using Apache Camel 2.15 with JMS in my application. Our JMS provider is customized Tibco (tibjms). I'm using Java DSL to define the Camel context, Routes etc. The following code i

Re: camel-JMS Component Responses from multiple queues

2015-10-19 Thread Claus Ibsen
No that is not possible. camel-jms is for listening to one JMS destination. But some brokers allow to do composite queues such as ActiveMQ http://activemq.apache.org/virtual-destinations.html where you can define this on the broker level, so N+ queues can appear as 1 JMS destination. On Tue, Oc

Re: camel+jms+TLS

2015-08-04 Thread Christian Müller
Which version of Camel do you use, how do you configured it, how does your route look like? What do you mean with "everything is fine"? What do you mean with "messages are consumed by camel, but I cant see anything in the queue"? You have to put more effort in describing your problem, if you reall

Re: camel-jms asyncStartListener Issue

2015-06-02 Thread yogu13
ok .. i got the code working, i was mistaken to think there was a timeout happening, but actually there wasnt.. All is good now.. Thank you! Regards, -Yogesh -- View this message in context: http://camel.465427.n5.nabble.com/camel-jms-asyncStartListener-Issue-tp5767551p5767816.html Sent from

Re: camel-jms asyncStartListener Issue

2015-05-27 Thread yogu13
Spliting the logic and taking less time for creation of connection worked... There seems to be a timeout happening somewhere underneath Let me see if i can build a testcase to showcase this. Regards, -Yogesh -- View this message in context: http://camel.465427.n5.nabble.com/camel-jms-asyncSta

Re: camel-jms asyncStartListener Issue

2015-05-27 Thread yogu13
Hello Claus, I understand what you say ... but what puzzles me is when asyncStartListener is set to false .. it works like a charm.. if a timeout was happening it should have been consistent. I am going to try splitting the logic for creation of InitialContext and actual creation of connection fr

Re: camel-jms asyncStartListener Issue

2015-05-27 Thread Claus Ibsen
Its using the connection factory to create the connection, so any timeout must come from the vendor of the jms client if they offer such kind. ActiveMQ has connection timeout options etc. Camel uses the JMS API and there is no such timeout, so you have to look at WebLogic to see what they offer.

Re: Camel jms listener on JMSReplyTo bahaviour

2015-01-14 Thread Ettoregia
Hi contactreji, thanks for your reply. I'm getting my response back through http with 200, but that is just an ACK. The point is, once the Camel rest consumer received the msg, that same msg is produced to a JMS queue, where an external application will read the message and at some point will sen

Re: Camel jms listener on JMSReplyTo bahaviour

2015-01-13 Thread Reji Mathews
Hey Ett I understand that u are sending request via REST request. You should be getting the response as a REST response with some http status codes isn't it ? Why are you polling the jms queue for the response from your processor . It should already build build a response and send it back to ur

Re: Camel JMS consumer route start / stop issues

2014-11-13 Thread Claus Ibsen
Try only use suspend/resume or stop/start and not mix and match them On Thu, Nov 13, 2014 at 10:16 AM, sushil_vsk5 wrote: > Guys, any thoughts on this > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Camel-JMS-consumer-route-start-stop-issues-tp5758893p5759030

Re: Camel JMS consumer route start / stop issues

2014-11-13 Thread sushil_vsk5
Guys, any thoughts on this -- View this message in context: http://camel.465427.n5.nabble.com/Camel-JMS-consumer-route-start-stop-issues-tp5758893p5759030.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: camel-jms 2.14.0 option validation on startup from an expression

2014-10-30 Thread sandp
I was able to get over the issue by setting disableReplyTo=true on the producer endpoint. -- View this message in context: http://camel.465427.n5.nabble.com/camel-jms-2-14-0-option-validation-on-startup-from-an-expression-tp5757289p5758344.html Sent from the Camel - Users mailing list archive a

Re: camel-jms 2.14.0 option validation on startup from an expression

2014-10-29 Thread sandp
Hi, I'm using the recipientList to pass *timetoLive *option dynamically. The issue I'm facing is that the consumer does send a replyTo, if I use a recipientList . If I use a static URL, it sends back a replyTo the queue. How do I get around this? *The route below does not produce a replyTo* =

Re: camel-jms consumer 2.14.0 on JBOSS EAP 6.1.1. connectionFactory must be specified

2014-10-27 Thread sandp
Not sure what the problem is, after a couple of refreshes and builds it worked. Looks like a environment related issue (Eclipse, Maven) -- View this message in context: http://camel.465427.n5.nabble.com/camel-jms-consumer-2-14-0-on-JBOSS-EAP-6-1-1-connectionFactory-must-be-specified-tp5758089p5

Re: camel-jms consumer 2.14.0 on JBOSS EAP 6.1.1. connectionFactory must be specified

2014-10-27 Thread sandp
It works when I add the *connectionFactory* option to the route, but my question is even though the jms component is initialized with JmsConfiguration containing the ConnectionFactory, why is the consumer expecting the connectionFactory option on the endpoint again? ===Consumer Route=

Re: Camel JMS message topic handling

2014-10-25 Thread ddewaele
That's true, but in Camel a Spring JMS AbstractPollingMessageListenerContainer implementation is used. After the thread finished processing the message, it does this: finally { JmsUtils.closeMessageConsumer(consumerToClose); JmsUtils.

Re: Camel JMS message topic handling

2014-10-25 Thread Minh Tran
Durability is only applicable when the consumers go offline. In your case, the consumer never goes offline, JMS will guarantee delivery of the message to the subscriber regardless of how slow it is consuming any prior messages. If that consumer goes offline then that’s a different story. On 2

Re: Camel JMS message topic handling

2014-10-25 Thread ddewaele
I think messages will be delivered “at most once” and non-durable subscribers can miss messages if they are inactive. In the case of camel, it is is a polling consumer, meaning that 1. it is started 2. it starts receiving messages (respecting timeouts) 3. it is stopped (becomes inactive) Accordi

Re: Camel JMS message topic handling

2014-10-24 Thread Minh Tran
I’m not sure how it all works internally but consumers on topics do not lose incoming messages while it is busy processing one message. That would break the rule of JMS guaranteed message delivery. I’ve had a number of projects using a topic with only one consumer on it. Normally the topic is

Re: Camel JMS message topic handling

2014-10-24 Thread ddewaele
As there is only 1 thread where a JMS Consumer is active (to avoid duplicate msg processing), isn't it normal that messages get lost in this scenario ? When that thread is busy processing a message (DefaultJmsMessageListenerContainer(AbstractPollingMessageListenerContainer).doReceiveAndExecute), a

Re: Camel JMS message topic handling

2014-10-21 Thread ddewaele
Interesting we had a similar issue with the MQTT endpoint http://camel.465427.n5.nabble.com/Camel-Endpoint-Consumer-startup-td5757635.html There the endpoint was also started (causing TCP connections to be established) before any consumers became active (resulting in loss of messages). I'll

Re: Camel JMS message topic handling

2014-10-21 Thread Minh Tran
I found this similar behaviour as well. http://mail-archives.apache.org/mod_mbox/camel-users/201404.mbox/%3cf54f1c39-dd8a-4c17-a51d-c564f3230...@winning.com.au%3E Appears as though the topic subscription is not guaranteed to happen before the camel context finishes starting up. So if the messag

Re: Camel JMS message topic handling

2014-10-21 Thread ddewaele
We're using the Camel ActiveMQ endpoint (http://camel.apache.org/activemq.html) and have setup a consumer in our route via the following URI : *activemq:topic:TopicName*. -- View this message in context: http://camel.465427.n5.nabble.com/Camel-JMS-message-topic-handling-tp5757853p5757857.ht

Re: Camel JMS message topic handling

2014-10-21 Thread Charles Moulliard
Hi, We have different unit tests within the Apache Camel project using a Topic and they work perfectly Which component do you use (camel-activemq, camel-jms or camel-sjms) ? Examples : - https://github.com/apache/camel/blob/master/components/camel-jms/src/test/java/org/apache/camel/component/jms/

Re: camel-jms consumer 2.14.0 on JBOSS EAP 6.1.1.

2014-10-08 Thread sandp
Its a xerces dependency issue in pom.xml. -- View this message in context: http://camel.465427.n5.nabble.com/camel-jms-consumer-2-14-0-on-JBOSS-EAP-6-1-1-tp5757369p5757391.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: camel-jms 2.14.0 option validation on startup from an expression

2014-10-01 Thread Claus Ibsen
Hi See this FAQ http://camel.apache.org/how-to-use-a-dynamic-uri-in-to.html On Wed, Oct 1, 2014 at 7:44 PM, sandp wrote: > Hi, > Camel is trying to validate the option value *for correct Type *against the > value of an expression on start up. For *timeToLive* option, the JMS > endpoint fails the

Re: Camel JMS Spring Remoting and Google Protocol Buffers

2014-06-15 Thread Maurice
OK, i have solved the problem and it is not a Camel or ActiveMQ but a Protocol Buffers issue. I do not understand the problem yet but this does not work with ZXing: But if i do this it decoding works Only by creating a local reference to a copy of an internal byte array of ByteString. -- Vi

Re: Camel JMS - memory leaking with IBM MQ

2014-05-31 Thread Paolo28
Yes but for me resource pooling/caching and resource cleanup are two different things. If I did not use Camel but plain Java I would not face this issue even with MQQueueConnectionFactory (no wrappers) ... -- View this message in context: http://camel.465427.n5.nabble.com/Camel-JMS-memory-leak

Re: Camel JMS - memory leaking with IBM MQ

2014-05-26 Thread Minh Tran
Hi My understanding is that the JMS connection factories were built for use in a J2EE container and if you are using them outside of one, which sounds like you are, then it must be wrapped in either Spring's CachingConnectionFactory or ActiveMQ's PooledConnectionFactory. Though I have read in

Re: Camel JMS - memory leaking with IBM MQ

2014-05-26 Thread Paolo28
Conclusion: I have solved the issue few days ago by using Spring CachingConnectionFactory which wraps MQQueueConnectionFactory - I was aware of this possibility but I could not believe it can create memory leak. I still don´t understand it and IMO this is bug (MQ?). -- View this message in c

Re: Camel JMS - memory leaking with IBM MQ

2014-05-21 Thread Paolo28
Hi, I use IBM MQ not ActiveMQ but I considered wrapping MQ conn. factory with Spring impl. but anyway caching is always about performance boosts so the calling code does not create expensive objects over and over if not needed. However if not caching it should not result in memory leak. Resoruces

Re: Camel JMS - memory leaking with IBM MQ

2014-05-21 Thread Willem Jiang
Did you use cached or pooled connection factory just as this[1] suggested ? [1]http://activemq.apache.org/jmstemplate-gotchas.html -- Willem Jiang Red Hat, Inc. Web: http://www.redhat.com Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weib

Re: Camel JMS component tied to Spring framework - bad news

2014-03-22 Thread Reji Mathews
Did you try modifying the Jboss Fuse example - cbr and try creating an activemq bean and send data through camel routes? On Sun, Mar 23, 2014 at 10:00 AM, sumeetkoshal wrote: > Hello All > Can you please advise if there is anyway to use blueprint file in an osgi > container to connect to third p

Re: Camel JMS component tied to Spring framework - bad news

2014-03-22 Thread sumeetkoshal
Hello All Can you please advise if there is anyway to use blueprint file in an osgi container to connect to third part JMS provider? If yes, can you please provide a sample? Regards Sumeet Email: sumeetkos...@hotmail.com -- View this message in context: http://camel.465427.n5.nabble.com/Came

Re: Camel JMS Queue Selector Problem

2014-01-17 Thread Claus Ibsen
Hi This is maybe fixed in a newer release. Try upgrading as we suggest here http://camel.apache.org/support On Fri, Jan 17, 2014 at 12:43 PM, Edwin wrote: > Using 2.10.3 > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Camel-JMS-Queue-Selector-Problem-tp5746138p574

Re: Camel JMS Queue Selector Problem

2014-01-17 Thread Edwin
Using 2.10.3 -- View this message in context: http://camel.465427.n5.nabble.com/Camel-JMS-Queue-Selector-Problem-tp5746138p5746147.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Camel JMS Queue Selector Problem

2014-01-17 Thread Claus Ibsen
What version of Camel do you use? On Fri, Jan 17, 2014 at 11:20 AM, Edwin wrote: > Hi Folks, > > I am encountering some issues when trying to implement a selector of a JMS > queue. My route is defined in the Spring DSL as follows: > > > > > > >

Re: camel jms polling

2014-01-08 Thread Tarun Kumar
Thanks. That works! On Thu, Jan 9, 2014 at 1:28 AM, Christian Posta wrote: > give your timer name something unique for each route: > > http://camel.apache.org/timer.html > > On Wed, Jan 8, 2014 at 9:11 AM, Tarun Kumar > wrote: > > Here problem is both routes are running sequentially. I tried wi

Re: camel jms polling

2014-01-08 Thread Christian Posta
give your timer name something unique for each route: http://camel.apache.org/timer.html On Wed, Jan 8, 2014 at 9:11 AM, Tarun Kumar wrote: > Here problem is both routes are running sequentially. I tried with > > > defaultProfile="true" poolSize="10" maxPoolSize="20" maxQueueSize="1000" > > r

Re: camel jms polling

2014-01-08 Thread Tarun Kumar
Here problem is both routes are running sequentially. I tried with as well, doesn't help. On Wed, Jan 8, 2014 at 10:08 PM, Tarun Kumar wrote: > Hi, > > I have two routes > > > > > > > > > > > > > > > > > > > > in bean1 and bean2, i poll messages from different JMS queues. When i > s

Re: Camel JMS monitoring

2014-01-02 Thread Claus Ibsen
On Fri, Jan 3, 2014 at 6:57 AM, Richa wrote: > I would also like to know if we can use hawtio project for commercial use. > Yeah hawtio is ASL2 licensed, so you can basically do (almost) whatever you want to do with it - also commercial. http://hawt.io/faq/index.html And if you have any code cha

  1   2   >