Hi,
Martin C. wrote:
>
> At the moment, I am using a Spring JmsTemplate approach. The Spring
> JmsTemplates work with polling (i.e. blocking call on receive()) and sets
> up the transaction before. This works fine.
>
I've now put together a very minimal example of what I'm originally trying
t
That sounds like a disk limit as each send/commit will cause a file sync and
the client is blocked till that completes. With batching, things improve as
the disk writes coalesce.
It may be interesting to run this little disk benchmark that replicates the
kahaDB writer thread to quantity the effect
I use ActiveMQ 5.3.1 with default configuration.
My message producer rate for 1 msg / per commit cannot exceed 90msgs/second.
I tried using multiple Thread/Sessions, Connections and JVM instances and
the rate cannot exceed this (without settings like
factory.setUseAsyncSend(true) )
The weirdest
I'm trying to configure embedded ActiveMQ on Tomcat 6.0.26 with JNDI. What
I'm trying to achieve is to have a clustered system. Tomcat is clustered and
I also want the embedded MQ server to be clustered too. I am avoiding XBean
and I chose to use Broker URI instead.
This is my ActiveMQConnectionF
You need to use a transacted session and rollback on an error to get client
side redelivery. See the redelivery policy test for examples:
http://svn.apache.org/viewvc/activemq/trunk/activemq-core/src/test/java/org/apache/activemq/RedeliveryPolicyTest.java?view=markup
On 27 April 2010 10:40, Patric
Hi community,
I'm facing an issue with the following setup.
ActiveMQ version: 5.3.1 embedded via xbean configured
Persistent queue (Kaha)
OS: CentOS java 1.6
App server: Tomcat with spring
I have one consumer (one async session with INDIVIDUAL_ACKNOWLEDGE). If I don't
acknowledge a message due t
