Sorry for my inaccurate post.
The behavior that the broker discards messages for the slow non-durable
subscription
depends on the maximum pending messages of the subscription.
There is a pending message limit strategy for the subscription called
PendingMessageLimitStrategy.
You may post your bro
Hi, I assume you're using non-durable subscription.
If so the eviction strategy will be involved when the memory consumption of the
broker exceeds the memory limit.In your case the producer is faster than the
consumer.
This cause more and more messages are pending in memory in the broker
and even
On Thu, 2013-01-10 at 21:52 +0100, Karel Gardas wrote:
> Hello,
>
> I'm playing a bit with ActiveMQ 5.7.0 and found that under some
> circumstances my subscriber looks like losing messages which are
> delivered to him from the broker. Honestly speaking I don't know if to
> blame subscriber or bro
Hello,
I'm playing a bit with ActiveMQ 5.7.0 and found that under some
circumstances my subscriber looks like losing messages which are
delivered to him from the broker. Honestly speaking I don't know if to
blame subscriber or broker in this case but while looking into web
console of the broker,
On Thu, 2013-01-10 at 12:37 -0800, Alex1 wrote:
> Look at the open issue db, and also the stack trace, it looks like very much
> the case AMQCPP-422.
>
> It traced back from IOTransport->fire
> Transportfilter::fire
> InactivivtyMonitor::OnException
> InactivivtyMonitor::stopMonitorThread
> synch
Look at the open issue db, and also the stack trace, it looks like very much
the case AMQCPP-422.
It traced back from IOTransport->fire
Transportfilter::fire
InactivivtyMonitor::OnException
InactivivtyMonitor::stopMonitorThread
synchronized()
decaf::util::concurrent::Lock
The pure virtual happens
Addingresolved the issue for me.
Many thanks for the idea.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Redelivery-policy-broken-in-5-7-0-tp4658304p4661611.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
James, it'd be of great help if you could create a test case of some
sort, so this could be investigated.
Regards
--
Dejan Bosanac
--
Red Hat, Inc.
FuseSource is now part of Red Hat
dbosa...@redhat.com
Twitter: @dejanb
Blog: http://sensatic.net
ActiveMQ in Action: http://www.ma
Hi,
that looks strange, maybe your client is also using some setup that
keeps it at 100MB. The best thing to do is to enable debugging on
org.apache.activemq.transport package and see in the logs what they
negotiate.
You should see something like
2013-01-10 17:04:11,753 [0.1:61616@54421] - DEBUG
On Wed, 2013-01-09 at 18:49 -0800, Alex1 wrote:
> activemq-cpp, version 3.4.0
> REdhat LInux
>
> Built activemq-cpp with openssl enabled.
>
> The server is configured with openssl enabled. The broker's certificate is
> set on client side
> with setSystemProperty(). Client test seems working fine
On Thu, 2013-01-10 at 06:05 -0800, stekreg wrote:
> Hi,
>
> I would like to use activemq-cpp on different machines and many of them are
> linux machines with limited resources which means the library size is an
> issue. I do not need the total bunch of features activemq-cpp offers,
> nevertheless
Greetings,
We caught an accident when already sent messages were unexceptedly
redelivered after rebuilding KahaDB index.
Full chronicle:
1. We noticed that counter of one queue shows 302 messages in the queue,
although its consumer receives nothing. When new message had appeared it was
instantly c
Hi,
I would like to use activemq-cpp on different machines and many of them are
linux machines with limited resources which means the library size is an
issue. I do not need the total bunch of features activemq-cpp offers,
nevertheless activemq is the tool of choice. I tried to use some of the
bui
Hello,
I'm playing a bit with ActiveMQ 5.7.0 and found that under some
circumstances my subscriber looks like losing messages which are
delivered to him from the broker. Honestly speaking I don't know if to
blame subscriber or broker in this case but while looking into web
console of the brok
activemq-cpp, version 3.4.0
REdhat LInux
Built activemq-cpp with openssl enabled.
The server is configured with openssl enabled. The broker's certificate is
set on client side
with setSystemProperty(). Client test seems working fine when certificate
verification succeeds.
Problem occurred when t
Hi Guys,
I would need help on the following.
Currently I'm using activemq 5.6 and trying to send files that is above
100MB.
I understand that the default configuration for wireFormat.maxFrameSize is
100MB.
The configuration is as below:
But I still encounters error s
Thanks for the quick reply.
Yes, the network and the machine load were the prime suspects at first, but
then we deployed a second broker with the same config but different ports on
the same host, and a test application started opening / closing connections
to both of the in parallel every couple o
17 matches
Mail list logo
