Re: NettyConnector explicitly initializes SSLContext instead of using default

Hi This is a question for Apache ActiveMQ user forum. On Tue, Jun 6, 2017 at 12:36 AM, mevans7 wrote: > BOTTOM LINE: > I need a secure way to initialize the SSLContext in > org.apache.activemq.artemis.core.remoting.impl.netty.NettyConnector. (No > keystore password in system properties.) > > US

Re: Possible bug in camel-ignite Component

Hi Gary Yeah a fix on github PR is much appreciated. On Mon, Jun 5, 2017 at 11:55 PM, Gary Hodgson wrote: > Hi > > I was playing with the camel-ignite component and ran into what appears to > be a bug. > > Creating an IgniteComponent from configuration works fine, but when I try > and create on

NettyConnector explicitly initializes SSLContext instead of using default

BOTTOM LINE: I need a secure way to initialize the SSLContext in org.apache.activemq.artemis.core.remoting.impl.netty.NettyConnector. (No keystore password in system properties.) USE CASE: I'm trying to configure a client to read JMS messages from Wildfly using SSL. This works ONLY if I specify

Possible bug in camel-ignite Component

Hi I was playing with the camel-ignite component and ran into what appears to be a bug. Creating an IgniteComponent from configuration works fine, but when I try and create one from an existing Ignite instance it throws an exception when starting the component. Looking at the code here https://g

trouble with camel spring web example

I am trying to work through an example from the camel website, namely camel-example-servlet-tomcat. I want to get a web application working that takes input from a web service request and uses it as the data with which to start a camel route. I am running Tomcat 7.0.63, Netbeans 8.02, Windows 10

Re: JettyClient failed cause by: HttpConnectionOverHTTP

owain wrote > Hi, > > My understanding is that you should not be using camel jetty as a producer > since it is deprecated. > > http://camel.apache.org/jetty.html > ; > > I would suggest using http4 component (http://camel.apache.org/http4 >

Re: activemq store percent is very high

As Taarriq said, this is a question for ActiveMQ, but having dealt with a similar problem recently here's some pointers: http://activemq.2283324.n4.nabble.com/KahaDB-vs-LevelDB-td4706599.html#a4706648 http://activemq.apache.org/kahadb.html#KahaDB-Multi(m)kahaDBPersistenceAdapter Cheers Doug On

Re: Bug in the camel - JDBC

Starnge, If I remove CamelHeaders after JDBC Insert No Exception arise in the JDBC Select. If CamelHeaders Present then Statement is Closed Exception arise. -- View this message in context: http://camel.465427.n5.nabble.com/Bug-in-the-camel-JDBC-tp5801823p5801837.html Sent from the Camel - User

Re: Camel jdbc - select batch processing

Simple solution is* Splitter with Collate* collate(200) -- View this message in context: http://camel.465427.n5.nabble.com/Camel-jdbc-select-batch-processing-tp5801682p5801832.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Bug in the camel - JDBC

Try set resetAutoCommit=false On Mon, Jun 5, 2017 at 12:17 PM, raja wrote: > Hi, > While working in the camel JDBC, I got Exception state that "Statement > is closed" > > My Route: > > > > > > > I can able to Insert.There is no problem while Insertion.

Bug in the camel - JDBC

Hi, While working in the camel JDBC, I got Exception state that "Statement is closed" My Route: I can able to Insert.There is no problem while Insertion. But I am getting Exception in the JDBC Selection Exception Message :The statement is closed.

Re: activemq store percent is very high

Hi This is really an activemq question, but the short answer is to clear the DLQ periodically. Cheers On 05 Jun 2017 09:54, "tnk" wrote: > Hi, > > i have simple camel route, which reads from activemq queue and sends email > messages, if exception occurs message is moved to dead letter queue. T

activemq store percent is very high

Hi, i have simple camel route, which reads from activemq queue and sends email messages, if exception occurs message is moved to dead letter queue. The problem is, store percent usage is very high. 10 messages in DLQ consumes 30% store (limit for storage is 1 gb), it is ~30mb for one message, but