On Wed, Nov 19, 2008 at 4:16 PM, Ashwin Karpe <[EMAIL PROTECTED]> wrote:
>
> The reason for piling up of messages on the queue is due to single threaded
> consumers connected through a non-pooled connection factory.
[cut]
Thanks for answer, we've added concurrent consumers and connection
factory from service mix as:
<bean id="connectionFactory"
class="org.apache.activemq.pool.PooledConnectionFactory">
<property name="connectionFactory">
<bean class="org.apache.activemq.ActiveMQConnectionFactory">
<property name="brokerURL" value="tcp://localhost:61616" />
</bean>
</property>
<!--Configure maximum connections used by the pool -->
<property name="maxConnections" value="10" />
<!--Configure maximum sessions per connection -->
<property name="maximumActive" value="5" />
</bean>
The times for one connector are betters, but for second remains on the
same level it's so strange because both connectors derived nearly same
code - measured times still consider queue. We try with your factory,
if it get us some better times.
Best regards,
Adrian
