Camel RestConfiguration bindingMode

I have a Camel REST component that I use to process a JSON message when a clients POSTs a JSON string. The idea is that the conversion to a POJO is handled by the Camel / REST component. This is how my route is configured : This was working fine at some point but all of a sudden I started gettin

Re: Camel JMS message topic handling

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

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

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

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

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

Camel JMS message topic handling

We were testing ActiveMQ topics with Camel and noticed the following behaviour: - Our Camel route was up and running with an activemq topic consumer. - Messages were published on the topic whle the route is active. - our Camel JMS consumer that was listening on that topic didn't receive all messag

Re: Camel Endpoint / Consumer startup

OK. We'll test with this on monday first thing. Are Camel snapshots automatically built and published on a remote maven repo somewhere ? If we point to 2.15-SNAPSHOT we should be good to go ? Is there a release schedule available for Camel so we can have a look when 2.15 is scheduled for rel

Re: Camel Endpoint / Consumer startup

Just had a quick look at the commit, but won't we still have the issue that the endpoint will be creating the connection to the broker (and as a result messages will start flowing). By the time the first consumer will be added messages will be lost. (Camel always needs to start the endpoint first

Re: Camel Endpoint / Consumer startup

I'll keep an eye out for the JIRA. Currently created my own MQTT endpoint component that also delays the connection and lets each consumer / producer start a connection. But consider this a hack / workaround. i think the Camel MQTT component needs some attention. But I'm willing to test / help /

Camel Endpoint / Consumer startup

I've run into this issue with the MQTTEndpoint where the MQTT endpoint is started (causing the MQTT connection to be established). As a result, the flow of mqtt messages is started *before* any consumers of that endpoint are registered. This puts the guaranteed delivery aspect of MQTT quality of s

Re: Camel MQTT Endpoint reconnect on transport failure

Created a ticket yesterday in the camel mqtt component https://issues.apache.org/jira/browse/CAMEL-7914 -- View this message in context: http://camel.465427.n5.nabble.com/Camel-MQTT-Endpoint-reconnect-on-transport-failure-tp5757564p5757588.html Sent from the Camel - Users mailing list archive

Camel MQTT Endpoint reconnect on transport failure

We're using the MQTT endpoint end noticed that when there is a transport failure the endpoint simply disconnects the connection but never connects again. Attempting to publish messages using this endpoint results in a failure : java.lang.IllegalStateException: Disconnected Is this by design or i

Re: CXFEndpoint and SOAPAction HTTP header

ils.cast((Map)message.get(Message.PROTOCOL_HEADERS)); headers.remove("SOAPAction"); } } } For some strange reason I wasn't able to create a new SpringBus bean under a different name. I had to use the existing "cxf" beanId for it to work. ddewaele w

Re: CXFEndpoint and SOAPAction HTTP header

endpoint capable of accepting different type of SOAP payloads ? ddewaele wrote > I'm using the cxfEndpoint in my camel flow to act as a webservice > producer. > > I have a number of clients that are able to send SOAP messages to that > endpoint, where Camel does the > required

CXFEndpoint and SOAPAction HTTP header

I'm using the cxfEndpoint in my camel flow to act as a webservice producer. I have a number of clients that are able to send SOAP messages to that endpoint, where Camel does the required processing and returns either a valid SOAP response or a SOAP fault. http://localhost:9080/app/webser

Camel cxfEndpoint testing guidelines

I wanted to verify if the approach below is the correct one regarding Camel cxfEndpoint usage and testability. I have a camelRoute using an cxfEndpoint (payload dataformat) to consume webservice messages. http://localhost:9080/app/webservices/service1"; endpointN

Re: Integrating 2 deployable units (containing camel routes)

Hi Christian, I was a bit confused by the documentation (does the direct-vm contain a copy/paste error ? It basically says the same as on the vm page). Both "support communication across CamelContext instances" but yet they differ ? It's also not clear that both can be used for inter OSGI bundle c

Integrating 2 deployable units (containing camel routes)

Hi, We have 2 deployable units, EBA files , containing camel routes that are deployed on Websphere. For those that don't know what an EBA is, it's an enterprise bundle archive (basically an EAR file containing OSGI bundles). We would like to have the ability to send messages that are being proc

Camel - Commons Configuration

Our application has a configuration repository based on Apache Commons Configuration. We're using commons configuration because we like the configuration file reloading strategies and the ability to combine several configuration files (to solve the issue of dealing with environment specific proper

Re: Camel multiple (nested) routes in one context

Hi, We're a couple of days away from going into production so we're not going to change the camel version. But I will upgrade to the latest version of Camel and re-test it soon For the moment we just moved the onExeption component outside of the flow. -- View this message in context: h

Re: Camel multiple (nested) routes in one context

Hi, We're using 2.10.1. Any idea about the logging (don't know if this is related) ? The fact that it added "complex-route" instead of "main-route" in the log for an exchange that never entered the complex-route ? [Camel (camelContext) thread #8 - vm://input] complex-route - Using real dispatche

Re: Camel multiple (nested) routes in one context

* logging : why it uses complex-route and not main-route in the logging for the "Using real dispatcher" log statement. (again for exchanges that never went into the complex-route. I've put the 2 snippets in the following Gist as well : https://gist.github.com/ddewaele/5097516 The

Camel multiple (nested) routes in one context

Hi, I have a Camel Spring XML where I define a camelcontext containing 2 routes. The main route is embedded inside the camlContext. At some point in the main route, based on someCondition, I need to decide to do either * standard processing (here I just need trigger a single camel processor) *

Intercepting https endpoints with proxy config not working

Hi, I'm trying to intercept the following https endpoint using the camel:interceptSendToEndpoint component : (the app.proxy things are being fetched from a properties file and they work fine when not intercepted). Unfortunately, intercepting this endpoint doesn't work. If I remove the proxy pa

Re: Configuring the Camel http4 component

namic endpoint uris and http/https connection pooling capabilities being lost ? Claus Ibsen-2 wrote > Hi > > See this FAQ > http://camel.apache.org/how-do-i-use-dynamic-uri-in-to.html > > > On Thu, Feb 7, 2013 at 2:44 PM, ddewaele < > ddewaele@ > > wrote: >

Configuring the Camel http4 component

We are currently using the Camel http4 component to perform both http and https calls either directly or through a proxy. All these scenarios work by configuring the http4 component in a certain way ex: plain http without proxy ex: https without proxy ex: https with a proxy I had 2 questions

Re: Camel as an OSGI bundle - OSGI detection strategy

Donald Whytock wrote > The preferred way in OSGI is having a BundleListener listen for a > STARTED event. You'd put this in the bundles that are trying to > create routes. As soon as my bundle containing the camel route is started, the Spring OSGI extender kicks in, and immediately refreshes my s

Camel as an OSGI bundle - OSGI detection strategy

Hi, I'm deploying Camel as an OSGI bundle (part of an EBA) on Websphere using the Spring OSGI extender. When the bundle is started, the camelContext is started and the route is up and running. I did notice however that it is not detecting that it is running in an OSGI environment and as such is n