The counter is managed on the server I presume, so I don't expect it to be
part of the transaction.
What I'm wondering though is why even after a consumer.close(),
session.close(), connection.close() the consumer stays connected to the
server ?
On Thu, Oct 16, 2014 at 8:26 PM, David Jencks <
davi
Maybe the redelivery counter is transactional so if the xa tx rolls back and
redelivery is needed the counter gets reset? this is speculation but might
explain your result.
david jencks
On Oct 16, 2014, at 10:45 AM, Xander Uiterlinden wrote:
> Hi,
>
> I'm trying to implement a JMS consumer
Hi,
I'm trying to implement a JMS consumer that uses XA transactions in order
to create a consumer that consumes the message and does work with the
message in a single transaction.
The code for the consuming worker is as follows:
class Worker implements Runnable {
public void run() {
Active
Has your broker been set up to be persistent, with a persistence store
configured? And are your messages flagged as persistent?
Also, how are you determining that the queues aren't persistent? What's
your test for that?
On Thu, Oct 16, 2014 at 9:36 AM, Kitewheel wrote:
> We currently have act
We currently have activeMQ setup to create dynamic queues. The problem is
they aren't persistent. Is there a connection string setting that can be
used to make the dynamically created queues persistent? We are running
version 5.8.0
--
View this message in context:
http://activemq.2283324.n4.
2. I believe (but haven't done it) that Individual will let you
acknowledge some messages (e.g. 1 and 3 but not yet 2), whereas Client
doesn't allow any gaps. Both of those allow you to ack the message at any
point during your handling of it (when you first receive it, when you're
completely done
In your broker-to-broker networkConnectors, are you using maxReconnects=0
as an argument to the failover URI? It wouldn't explain why amq4 got
demoted, but it could explain why messages aren't transferring to amq5
instead.
You say you've got duplex connections between the clusters; which cluster
I've created a working application loosely based on this example:
http://remark.wordpress.com/articles/transactional-message-processing-with-activemq-and-nms/
I'm able to publish and consume messages just fine although I haven't done
any performance testing.
My general requirements are
* Use NMS
I believe I may have found a bug here. However, this could also be a
mis-configuration on my side.
Before I go into a detailed description of my observation, here my setup:
I have setup the following system in a virtual environment:
I have 3 zookeeper nodes.
I have 6 ActiveMQ broker using 5.10.0
Which JDK are you using? I mean, its producer, platform
it runs on and if it's a 32 or 64 bits version.
--
Questo messaggio è di carattere riservato ed è indirizzato esclusivamente
al destinatario specificato. L'accesso, la divulgazione, la copia o la
diffusione sono vietate a chiunque altro ai
ActiveMQ service wrapper memory setting is:
# Initial Java Heap Size (in MB)
#wrapper.java.initmemory=3
# Maximum Java Heap Size (in MB)
wrapper.java.maxmemory=4096
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Error-Java-heap-space-viewing-queue-through-web-ui-having
In addition I also want to understand how does kahadb stores such big
messages ? Do I need to configure any persistent store parameter for
handling such big messages.
For ex: default journal size is 32MB, how will it store message larger thn
32 MB ?
Thanks,
Anuj
--
View this message in conte
Hi,
I am using ActiveMQv5.10.
I have a use-case where client sends message around 100MB.
Is there any limitation on the message size, (for JMS as well as stomp) ?
Thanks,
Anuj
--
View this message in context:
http://activemq.2283324.n4.nabble.com/ActiveMQ-message-size-limitation-tp4686438
We are using ActiveMQ version 5.8.0 on Java 1.6.
Currently when ActiveMQ queue contains lots of messages (says more than
400+), then clicking queue in ActiveMQ web UI use approx. 100% CPU/Memory
and ultimately dies with Java Heap space error.
Adding more memory parameters did not solve the probl
14 matches
Mail list logo
