Hi all,
In the scenario where a producer sends n messages in a transacted session
and an exception is thrown during commit (due to network issues for
example), what happens to those n messages sent (but not commited)?
Would they still live in memory in the broker?
Thanks,
Ozan
--
View this mes
Here are some suggestions:
1. Put "log4j.appender.console.threshold=INFO" (in the console appender) in
a new line - in your config it seems to be in the same line as the statement
above it.
2. You have configured SMTP appender for WARN+ only - double check that you
are generating warning messages
Best way to debug this is to put log4j.appender.MAIL.SMTPDebug=true and
restart AMQ. log4j will start emitting debug messages to stdout and you will
see what is going wrong.
There might be a problem with relay permissions or ports...
Ozan
--
View this message in context:
http://activemq.2283324
Thanks for your reply Jason!
That link you provided recommends the use of PooledConnectionFactory if I am
publishing messages - which is OK for B2 endpoint in my above example and
recommends using MessageListenerContainer for consuming messages which is
for B1 endpoint. This also correlates to an
Hi all,
I am trying to understand the most optimised way to send messages
concurrently between two activemq endpoints using Camel. There has been some
discussions on this in the mail groups but some of them confuses me even
more. So I am looking the draw the line under this topic and get your
recom
Hi Gary,
I downloaded the source, compiled and ran the test - indeed it works
perfectly fine. In order to understand where the problem is, I started to
make changes one at a time:
1. I replaced HUB with a clean deployment of AMQ 5.5 on a remote virtual
machine - no modifications to activemq.xml.
Thanks for your reply Gary.
>> When you get the WARN message, it is expected that the stats are wrong
>> because the store should not be getting duplicates.
OS - Agreed.
>> At the point that the store recognizes the duplicate, the stats and
>> cursors may have
>> already processed the message
Hi all,
I tried the below simple network of brokers test with ActiveMQ 5.5,
Activemq-5.5.0-fuse-00-43 and Activemq-5.5.0-fuse-00-27 and get the same
behavior with all of them.
I deployed ActiveMQ (above versions) to a virtual machine and my local box.
I made no changes in local instance. I only a
Possibly similar to https://issues.apache.org/jira/browse/AMQ-3473
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Message-loss-in-network-of-brokers-transactional-send-tp3588714p3766852.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Just created a JIRA for this: https://issues.apache.org/jira/browse/AMQ-3469.
This might actually be a bug.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Message-loss-in-network-of-brokers-transactional-send-tp3588714p3764707.html
Sent from the ActiveMQ - User mailing lis
Broker1 configuration:
http://activemq.2283324.n4.nabble.com/file/n3762374/activemq_-_broker1.xml
activemq_-_broker1.xml
Broker2 configuration:
http://activemq.2283324.n4.nabble.com/file/n3762374/activemq_-_broker2.xml
activemq_-_broker2.xml
--
View this message in context:
http://activemq.22
So let me summarize this thread from the beginning:
Please see this arch diagram:
http://activemq.2283324.n4.nabble.com/file/n3762364/ActiveMQ_-_Composite_Queues.png
ActiveMQ_-_Composite_Queues.png
I am sending 3000 messages from my producer into broker1 and observe message
counts in Transit an
Can you try activemq-admin instead of activemq? I.e. "bin\activemq-admin
create instance1"?
Ozan
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Running-multiple-activemq-instances-on-the-same-server-tp3758394p3760444.html
Sent from the ActiveMQ - User mailing list archive
>> "Also, I think a send transaction would help, it should encompass all of
the composite destinations."
That is correct. When I send messages in transaction, I get no message loss
- but both JMX and admin console pending message count displays wrong
number.
My setup is still same - 2 brokers, co
Hi,
I am having problems stopping a camel route which pushes messages from a
queue in broker1 to another queue in broker2. I am using Apache Camel
2.7.1-fuse-00-27 that ships with ActiveMQ 5.5.0-fuse-00-27.
The problem comes when there are inflight messages. This happens if broker2
is offline (be
Hi there,
Is it possible to let me know the disadvantages of disabling audit in kahadb
(apart from the obvious - duplicates won't be suppressed) please?
Thanks,
Ozan
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Message-loss-in-network-of-brokers-transactional-send-tp35
Thanks Gary. I can confirm that sending with transactions works perfectly but
slower than AUTO for my scenario where messages are generated one by one and
need to be sent one by one.
What are the disadvantages of disabling audit in kahadb (apart from the
obvious - duplicates won't be suppressed)?
Thanks Gary.
I've tested below with Fuse 5.5 (apache-activemq-5.5.0-fuse-00-27) and
unfortunately the issue is there. However what it boils down to is this
"suppressing duplicate message send" message in composite destinations.
In order to prove this is the case, I started eliminating components
Here is some more info:
I enabled debug logging and can see where the problem is (however I still
don't know what the solution is).
I ran my test again and send 5000 messages to one broker which is configured
to store-and-forward the message to broker2. Two brokers are connected via
network of br
Hi,
Can you please let me know whether there is a possibility of message loss in
composite queue configured as:
As far as I understand this from the documentation,
Hi,
Based on below test and my further tests where I kill the target broker
during store-and-forward operation, I am seeing messages lost/dropped.
Basically this problem occurs when messages are sent to a queue on one
broker which is configured to be "staticallyincluded" to forward messages to
an
I seem to be losing some messages in a network of brokers topology in the
following setup:
- 1 producer pushing messages to a persistent queue (let’s call it
“IN.QUEUE.Broker1”) on one broker (broker1) inside a transaction. Producer
commits in every 100 messages.
- IN.QUEUE is a composite queue w
Hi all,
What is the preferred way to reliably forward messages from an AMQ broker in
one datacenter (DC1) to another AMQ in another datacenter (DC2)?
Is it network of brokers - like:
OR by using jmsBridge between two brokers in each datacenter?
Cheers,
Oza
)
before it gets an ack back from the broker.
Do you think my conclusion is correct? If I add a couple of more queues for
Camel to multicast, would I see even decreased enqueue performance?
Any guidance is appreciated.
oseymen
--
View this message in context:
http://activemq.2283324.n4
24 matches
Mail list logo