Thank
A+JYT
--
View this message in context:
http://activemq.2283324.n4.nabble.com/system-property-tp4715105p4715446.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
or properties file
>
> A+JYT
>
>
>
> --
> View this message in context: http://activemq.2283324.n4.nab
> ble.com/system-property-tp4715105.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
:
http://activemq.2283324.n4.nabble.com/system-property-tp4715105.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Thanks for the feedback!
On Fri, Jun 28, 2013 at 8:27 AM, Gary Tully wrote:
> It was an effort to increase the write throughput, but for kahadb the
> bottleneck is the index so any gain/loss for different workloads was
> over shadowed.
> For the moment, stick with the defaults. The logging may
It was an effort to increase the write throughput, but for kahadb the
bottleneck is the index so any gain/loss for different workloads was
over shadowed.
For the moment, stick with the defaults. The logging may help identify
the best value for journalMaxWriteBatchSize.
On 27 June 2013 18:55, Chris
Maybe Gary can give you more info, but the caller buffer appender is an
experimental appender to help offload the buffering of writes to calling
threads and reduce the time spent in the thread that actually writes to the
journal. The write stat window is for logging purposes to get an idea of an
av
Hi,
I came across the following system properties that are uses by the
kahaDBPersistenceAdapter, their default values are:
-Dorg.apache.kahadb.journal.appender.WRITE_STAT_WINDOW=0
-Dorg.apache.kahadb.journal.CALLER_BUFFER_APPENDER=false
A particular unit test recommends setting them to:
-Dorg.a
Great, thank you very much for the change. Would you also consider
changing the type of the "rmiServerPort" property to the same type in
order to allow it to be overridden through a system property?
Regarding AMQ-2939, there seems to be a way to disable XML validation
programa
o be possible to override anymore
> the JMX connector port through a system property. Here is how I used to do
> it with version 5.3.0:
>
> - in activemq.xml file I define the following configuration
>
> connectorPort="${activemq.jmx.port}" />
>
>
> - then I
> the JMX connector port through a system property. Here is how I used to do
> it with version 5.3.0:
>
> - in activemq.xml file I define the following configuration
>
> connectorPort="${activemq.jmx.port}" />
>
>
> - then I add some system properties on
name
from a system property or something like that.
Is there recommended way to change the queue name without having to modify
xml files that are embedded in jars or recompile and change annotations?
--
View this message in context:
http://www.nabble.com/ActiveMQ-JBoss-MDB-Destination-From-System
..
acooper wrote:
>
> We're trying to use ActiveMQ (4.2-SNAPSHOT 06/07/07) on JBoss 4.0.4 and
> are running into an interesting problem - somehow ActiveMQ is managing to
> set a null system property. Null system properties are disallowed in Java.
> The property in question
We're trying to use ActiveMQ (4.2-SNAPSHOT 06/07/07) on JBoss 4.0.4 and are
running into an interesting problem - somehow ActiveMQ is managing to set a
null system property. Null system properties are disallowed in Java. The
property in question is org.apache.activemq.kaha.Store and is set i
13 matches
Mail list logo