Re: Urgent - Endpoint wsdl XSD's are stored in heap memory

My wsdls contain xsd's which are of 1MB size, All these xsd's are loaded in memory when context is loaded for the first time. I don't want these xsd's to be loaded in memory. Please let me know how to stop this -- View this message in context:

[ANNOUNCEMENT] Apache Camel 2.18.2 Released

The Camel community announces the immediate availability of the new Camel 2.18.2 patch release. This release contains 68 bug fixes and improvements applied in the past months by the community on the Camel 2.18.x branch. The artifacts are published and ready for you to download [1] either from the

Re: Specifying file names using Dropbox component

JIRA issue: https://issues.apache.org/jira/browse/CAMEL-10768 -- View this message in context: http://camel.465427.n5.nabble.com/Specifying-file-names-using-Dropbox-component-tp5793105p5793222.html Sent from the Camel - Users mailing list archive at Nabble.com.

How to set AMQP.BasicProperties on outgoing message using Camel?

Please share how to set AMQP.BasicProperties on outgoing message(s) using Camel. Expected RabbitMQ message: Exchange Displays the Exchange fine Routing Key Displays the Routing Key fine Properties content_encoding: UTF-8 /Unable to set this content_type: text/plain //Unable to set this

Re: allowUseOriginalMessage="false" with useOriginalMessage="true" - new camel.breadcrumbId value

Claus Ibsen-2 wrote > From Camel 2.18 onwards you will get an exception if you attempt to > access the original message and it was not allowed. Thanks Claus for clarifying. Ralf -- View this message in context:

Re: Specifying file names using Dropbox component

Hi Yeah it sounds like a good enhancement. You are welcome to log a JIRA http://camel.apache.org/support.html As a workaround you can use dynamic to http://camel.apache.org/how-to-use-a-dynamic-uri-in-to.html On Fri, Jan 27, 2017 at 12:54 PM, Tim Dudgeon wrote: > I'm

Re: NullPointer. org.apache.camel.component.jms.DefaultJmsMessageListenerContainer

Hi I suggest to report the NPE to the ActiveMQ mailing list or their JIRA as its a bug in their project On Sat, Jan 28, 2017 at 12:35 AM, darek wrote: > I wonder if you have solved this problem, if so I'd like to know how. > What version of activemq are you using?

Re: Loadbalancing with failover but remembering the unavailable endpoint

Hi No not with those OOTB load balancers from camel-core. They are a bit limited. You can build your custom load balancer, and extend some of the OOTBs or copy their code. If you want to use hystrix circuit breaker, then it has such a functionality but for calling one service. But you can use it

Re: Urgent - Endpoint wsdl XSD's are stored in heap memory

This is not possible. And what is your use-case for not storing something in heap memory? Its tiny data about a WSDL file and so on. If you want this on the first request, then you need to use dynamic uris http://camel.apache.org/how-to-use-a-dynamic-uri-in-to.html On Mon, Jan 30, 2017 at

Re: allowUseOriginalMessage="false" with useOriginalMessage="true" - new camel.breadcrumbId value

For your version of Camel you must yourself turn that allow on or off depending on your use it or not. >From Camel 2.18 onwards you will get an exception if you attempt to access the original message and it was not allowed. On Mon, Jan 30, 2017 at 3:58 PM, rsteppac2 wrote:

allowUseOriginalMessage="false" with useOriginalMessage="true" - new camel.breadcrumbId value

Hello all, I stumbled across a misconfiguration in one of my routes where the context did not allow the use of the original message: But by accident one of the routes had an onCompletion handler set to use the original message: I don't think the onCompletion handler acutally got the

Urgent - Endpoint wsdl XSD's are stored in heap memory

Request, response xsd mentioned in wsdl and all the xsds included in request, response xsds are loaded at the server start and stored in heap memory. How to avoid this? Please help -- View this message in context:

ZooKeeperPolicy not working in Camel 2.18.1 (?)

I would really appreciate if someone could help me get ZooKeeperRoutePolicy working asexpected... I have a zookeeper cluster with 3 servers and two karaf instances with the following route installed: from("timer://timer1?fixedRate=true=1") .routeId(routeId)