Thanks a lot for the checking. Please kindly let me know if any updates.
At 2013-06-17 23:23:24,"Christian Posta" wrote:
>Yah, I can verify this is the case. Threads leak because the
>threadpoolexecutor doesn't evict the threads. Checking for the best
>solution to this.
>
>
>On Sun, Jun 16, 201
I've closed the Jira, this is not an issue. You can take a look at the test
cases to see why. They're adapted from your orignal tests.
Cheers
On Mon, Jun 17, 2013 at 3:35 PM, Christian Posta
wrote:
> I've opened a JIRA here: https://issues.apache.org/jira/browse/AMQ-4586
>
> The workaround for
Hi!
We are seeing some inconsistent results when connecting via
Apache.NMS.ActiveMQ and setting consumer.prefetchSize=0 in the connection
uri.
Sometimes we see the consumer appear in the web console with Prefetch
Max pending showing as 1, which is what we expect.
However sometimes we see the d
Haven't tested it out too much, but I believe you should be able to do this
in the activemq.xml configuration file...
note you'll have to explicitly specify where you want to use
FilePendingMessageCursors if you have persistent=false
http://www.springframework.org/schema/beans";
class="o
It might be better to ask in the Camel mailing list.
Post your camel route. But it sounds like somehow your consumers aren't
cached propelry.
On Mon, Jun 17, 2013 at 6:39 AM, indrayani wrote:
> Hi All,
> I am using activemq with camel ,I have defined routes like :
>
> 1) from servletA to actimq
Make sure that your consumers/producers also properly failover to the
correct slaves.
On Mon, Jun 17, 2013 at 1:31 PM, Clement Buisson <
clement.buis...@lookout.com> wrote:
> Arf, my badŠ the current configuration is:
> I have 2 brokers. Broker A and Broker B with both one master A1/B1 and its
>
I've opened a JIRA here: https://issues.apache.org/jira/browse/AMQ-4586
The workaround for your case is to use the failover transport and you won't
see the executor threads leaked.
On Mon, Jun 17, 2013 at 11:23 AM, Christian Posta wrote:
> Yah, I can verify this is the case. Threads leak becau
Arf, my badŠ the current configuration is:
I have 2 brokers. Broker A and Broker B with both one master A1/B1 and its
slave A2/B2
I am using masterslave:/ instead of failover:/
A1:masterslave:(tcp://B1:62626,tcp://B2:62627)
A2:masterslave:(tcp://B1:62626,tcp://B2:62627)
B1:masterslave:(tcp://A1:
Hi,
EOFException means that client closed connection unexpectedly, so it might
be that clients just closes socket or network connection between brokers
goes away. But as far as I see from your messages you don't experience any
problems, so you should worry about it. Those debug messages from your
there is the discarding dlq plugin see:
http://activemq.apache.org/message-redelivery-and-dlq-handling.html
but it would be a nice enahancement to allow a discarding dlq strategy
to be specified via a policy entry.
I have opened https://issues.apache.org/jira/browse/AMQ-4584 to track this.
On 17
Yah, I can verify this is the case. Threads leak because the
threadpoolexecutor doesn't evict the threads. Checking for the best
solution to this.
On Sun, Jun 16, 2013 at 4:07 AM, lzr wrote:
> Dear all,
>
>
> I found a thread leak issue during try activemq 5.6:
> I create connection when sendin
Hi All,
I am using activemq with camel ,I have defined routes like :
1) from servletA to actimq A
2) from activemq A to servletB
3) from servletB to activemq C
4) from activemq C to servlet D
during first time request, the activemq works fine, but if i send the
request second time, I am getting f
In our project, we don't want any unused queue exists on our ActiveMQ server,
but one queue named DLQ will appear once one message is failed to devilry,
The DLQ will hold lots of disk space, is there any way to remove this queue?
I want these failed queue disappeared once they failed.
--
View t
13 matches
Mail list logo
