Re: Activemq consumer is closing

Hi, I am using apache-activemq-5.14.1 and getting the below issue. javax.jms.IllegalStateException: The Consumer is closed at org.apache.activemq.ActiveMQMessageConsumer.checkClosed(ActiveMQMessageConsumer.java:880) at

Re: Simple IN with empty value in list

fails as in gives you an exception or fails as in not the behavior you expected. On Thu, Dec 1, 2016 at 11:33 PM, Karts [via Camel] < ml-node+s465427n5790907...@n5.nabble.com> wrote: > Hi, > > I'm trying to use simple to test for an empty value in a list, so > something like: > >

Simple IN with empty value in list

Hi, I'm trying to use simple to test for an empty value in a list, so something like: simple("${body.stringValue} in ',gold,silver'") It doesn't seem to work though, if body.stringValue is '' this fails. -- View this message in context:

Re: Camel body is coming as null to processor

Hi, Claus had good tip with reading Stream twice. I just wanted to ask - does your public class DetailsInfoProcessorV2 implements org.apache.camel.Processor ? If so, it might be better/readable to "call processor" directly, instead of bean invocation. Cheers, Josef On Thursday 01 of

Re: Camel body is coming as null to processor

Hi See this FAQ http://camel.apache.org/why-is-my-message-body-empty.html On Thu, Dec 1, 2016 at 7:37 PM, reddy.janke wrote: > > > > logName="com.skandha.eim.air" /> > > ${body} >

Camel body is coming as null to processor

${body} I am able to print camel body from camel context. But when I am trying to unmarshal through ref or pass to processor Body convert as null and getting below

Re: camel-jms

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 -

Re: Throwing Disconnected Exception with camel-sjms

It seems the right way to run a camel application is by using /main.run()/ instead of /main.start()/ It solved almost all of my problems. -- View this message in context:

Re: stand-alone problem

Wow, it works. I have been struggling for two days as to why it would all of a sudden stop working. And to make matter worse, the connect/reconnect from spring that I reported in this post also started working. Thanks a log Claus.

Re: camel-jms

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

Re: stand-alone problem

Did you look here for an example for how to keep it running forever as a standalone app? http://camel.apache.org/running-camel-standalone-and-have-it-keep-running.html On Thu, Dec 1, 2016 at 4:29 PM, sa_james [via Camel] < ml-node+s465427n5790889...@n5.nabble.com> wrote: > So If I ditch spring

Re: stand-alone problem

Use the run method instead of start. On Thu, Dec 1, 2016 at 4:07 PM, sa_james wrote: > Here I am again with a simple test: > > /from("jms:queue").to("log:test")/ > > / class="org.springframework.jms.connection.CachingConnectionFactory"> >

Re: stand-alone problem

So If I ditch spring and go back to using setters, everything will be fine? -- View this message in context: http://camel.465427.n5.nabble.com/stand-alone-problem-tp5790885p5790889.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: stand-alone problem

I am not experienced with spring but it seems your context is started and then there is nothing to keeps it going to so it dies straight away. Normally with a Main() you need to add code to keep it running forever. Via blueprint or spring the context is injected.. On Thu, Dec 1, 2016 at 4:23 PM,

Re: stand-alone problem

If I set a breakpoint at the last statement, it will consumes messages from the queue. -- View this message in context: http://camel.465427.n5.nabble.com/stand-alone-problem-tp5790885p5790887.html Sent from the Camel - Users mailing list archive at Nabble.com.

stand-alone problem

Here I am again with a simple test: /from("jms:queue").to("log:test")/ / / After I have started the app: INFO Route: route1 started and consuming from: jms://queue INFO Total 1 routes, of which 1 are started. INFO Apache Camel 2.18.0 (CamelContext: camel-1) started in 0.481

Re: Durable subscriber on an Oracle Advanced Queue (Topic)

Found the solution to our problem. The problem was caused by a difference in character sets. The database uses WE8ISO8859P15 which is not directly supported. The difference can cause issues when setting the subscriber or reading / writing jmsproperties. The issue was solved by adding the ojdbc

Re: Throwing Disconnected Exception with camel-sjms

In case you wonder about the route, it is really simple: /from("jms:TEST") .to("log:test")/ Thx. -- View this message in context: http://camel.465427.n5.nabble.com/Throwing-Disconnected-Exception-with-camel-sjms-tp5790882p5790883.html Sent from the Camel - Users mailing list archive at

Throwing Disconnected Exception with camel-sjms

The ride continues between camel-jms and camel-sjms While consuming from a jms-queue, I would like to log exceptions when the queue has crashed. When I disconnect the queue from the network, camel-sjms does not thrown any exception. How can I do that? I tried with /

Re: camel-jms

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:

Re: camel-jms

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

camel-kafka 2.18.0 KafkaConsumer manual commit

Hi, i have a camel route consuming from kafka. When an unhandled Exception is thrown within that route i do not want the kafka offset to be committed. As a first step i set the autoCommitEnable property to false. This is my route: public static final String START_KAFKA_RECEIVER =

stand-alone starts and stops after switching to spring

Testing Spring reconnect with camel and I did configured the factory as follows: Sadly it does not reconnect. Anyway to achieve this? Thanks. -- View this message in context:

Re: Cassandra 3/CQL 3.4 support for camel-cassandraql component

And Camel 2.18.0 is already released. -- Andrea Cosentino -- Apache Camel PMC Member Apache Karaf Committer Apache Servicemix Committer Email: ancosen1...@yahoo.com Twitter: @oscerd2 Github: oscerd On Thursday, December 1, 2016 9:38 AM, Andrea Cosentino

Re: Cassandra 3/CQL 3.4 support for camel-cassandraql component

Cassandra 3.x is supported from Camel 2.18.0 The driver used in 2.18.x branch is the 3.1.0 -- Andrea Cosentino -- Apache Camel PMC Member Apache Karaf Committer Apache Servicemix Committer Email: ancosen1...@yahoo.com Twitter: @oscerd2 Github: oscerd On

Cassandra 3/CQL 3.4 support for camel-cassandraql component

Hi, Have tried camel from version 2.15.0 to 2.17.3 but have found that it still doesn't support Cassandra 3 or CQL version 3.4 yet. Currently I can see camel-cassandraql component supports Cassandra version 2.2.x (Ex - apache-cassandra-2.2.8) and CQL Version 3.3.x (Ex - CQL spec 3.3.1) Newer

AW: How to use the InOut (Request-Reply) pattern in combination with REST/Jetty?

Hi, ok, more or less got what was the problem (user mistake): I used SSH port forwarding on 61616 for the application/client to be able to connect to ActiveMQ (runs on a server that's hidden inside a private network). This does not work (of course) because ActiveMQ uses tcp sockets (at least I