Re: JMS Request Reply DMLC shutdown

There seems to be a cyclic bug in Camel regarding the shutdown of temporary queues. When stop() is called on the request reply JmsEndpoint the runningMessageListeners.get() count returns 1 preventing to call stop on ServiceSupport. Then inside the DMLC in refreshConnectionUntilSuccessful()

Re: JMS Request Reply DMLC shutdown

As a quick and dirty solution one can do this on bundle shutdown: JmsEndpoint jmsEndpoint = camelContext.getEndpoint(amq:queue:Endpoint, JmsEndpoint.class); jmsEndpoint.onListenerContainerStopped(null); This will decrement the runningMessageListeners (which should always be on for temp queues

JMS Request Reply DMLC shutdown

Dear Community, camel seems to not shutdown the spring DMLC in a JMS Request Reply with Camel Proxy scenario using: Karaf 2.3.4 Spring 3.2.8 ActiveMQ 5.9.0 Setup like in tutorial http://camel.apache.org/tutorial-jmsremoting.html Starting a bundle with temp queues is no problem and works like it

Re: Camel JMS Spring Remoting and Google Protocol Buffers

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. --

Camel JMS Spring Remoting and Google Protocol Buffers

Dear Community, i am successfully using Camel with Spring remoting over JMS using the default Java serialization. The interface used: String decode(byte[]image, String BarcodeType, String charset). Now i have to add access for a CPP using CMS client and the best cross language structure

JavaFX + Spring + Camel + Maven

Dear Community, i am trying to build a JavaFX standalone application using Spring as DI an Camel for routing. The application is working fine with Spring only using a modified FXML Loader: This is the context XML : As soon as i uncomment the camelcontext tags i get the following exception:

Re: JavaFX + Spring + Camel + Maven

To answer my own question, i am missing the entries from the spring.handlers and spring.schemas files from the camel-spring jar in my application Jar. Now how do i do that? -- View this message in context: http://camel.465427.n5.nabble.com/JavaFX-Spring-Camel-Maven-tp5749039p5749040.html Sent

Re: JavaFX + Spring + Camel + Maven

The solution is not a beauty but works with maven and Netbeans sofar: -- View this message in context: http://camel.465427.n5.nabble.com/JavaFX-Spring-Camel-Maven-tp5749039p5749046.html Sent from the Camel - Users mailing list archive at Nabble.com.

Headers CamelFileNameConsumed and CamelFileLength in Mail

Dear Community, after creating a error report with velocity in onexception, using some of the camel exchange header values, and sending it as an HTML email it shows the headers CamelFileNameConsumed and CamelFileLength on top of the mail markup: These are not represented in the .vm file in any

Re: Headers CamelFileNameConsumed and CamelFileLength in Mail

I was using CXF and the following did the trick. -- View this message in context: http://camel.465427.n5.nabble.com/Headers-CamelFileNameConsumed-and-CamelFileLength-in-Mail-tp5744231p5744236.html Sent from the Camel - Users mailing list archive at Nabble.com.

Producer template and spring xml defaultendpoint error

Using camel 2.11.0, Karaf 2.3.1. with blueprint. I am trying to send multiple messages using a custom processor to a tx-transacted jms endpoint with a ProducerTemplate according to l http://camel.apache.org/how-do-i-write-a-custom-processor-which-sends-multiple-messages.html . XML: template

Re: Producer template and spring xml defaultendpoint error

To my knowledge this is complete: ?xml version=1.0 encoding=UTF-8? blueprint xmlns=http://www.osgi.org/xmlns/blueprint/v1.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xmlns:cml=http://camel.apache.org/schema/blueprint;

Externalizable and the activemq classpath

Does activeMQ need our self created classes on its classpath if i externalize these objects into java primitive types? My research sofar indicates that a jms message type of bytestream with externalize should do the trick to avoid the classpath issue. -- View this message in context:

Best practice for paralell execution of xa transacted routes

A perfect question for a Monday: i have a amq queue with a message which contains instructions to execute specified modules as one unit of work. These modules may or may not use other datasources besides jms requireing a local or global (xa) transaction context. If a module requires the global

JMS(XA) component with a maxConcurrentConsumers value 1

I am using the config for jms xa transactions from the following website: https://access.redhat.com/site/documentation/en-US/Fuse_ESB_Enterprise/7.1/html/EIP_Transaction_Guide/files/XaJms-Sample.html

Re: JMS(XA) component with a maxConcurrentConsumers value 1

After some diggin in the spring docs i came up with a replacement for the jcaPooledConnectionFactory that should support consumer pooling: Springs CachingConnectionFactory. There are some restrictions, see http://tmielke.blogspot.de/2012/03/camel-jms-with-transactions-lessons.html

Camel JMS or ativeMQ component for xa transactions?

After implementing the workaround for ENTESB633, i noticed it uses the jms component as part of the xa transactions. In the camel docs it is clearly stated that the activemq-camel component should be used for amq. Is this also the case for xa transactions? -- View this message in context:

Re: Camel JMS or ativeMQ component for xa transactions?

Nothing new there, but why use the jms component on this workaround which connects to amq? This does not give much confidence on an issue that is already not working as it should. -- View this message in context:

Re: Camel JMS or ativeMQ component for xa transactions?

I will test both components and see if there are any issues, besides that the activemq-camel 5.8.0 component had to be modified to überhaupt play nice with Karaf :) . And i cannot oversee any issues concerning the ENTESB633 bug, so lets find out. -- View this message in context: