Hi,
Iam building an application on activemq where iam sending a message from
producer where my delivery mode is NON_PERSISTENT (*iam not dealing with
PERSISTENT delivery mode and i know it will be stored in DLQ-which is not my
design*)and have set a time to live for the message using
producer.setT
I hadn't heard of anyone using EFS before you asked about it. That's not
to say that no one has, just that I've got less idea than you do about what
if any pitfalls you might find along the way.
On Sep 21, 2016 10:33 AM, "khokhani" wrote:
> Thanks Tim! Thanks Justin! for insight on this topic.
Thanks Tim! Thanks Justin! for insight on this topic.
I have setup Amazon EFS as LevelDB persistence store and MySql based locker.
All functional and failover testing are positive and message are available
and delivered without any failure or loss while switching from master to
slave as well as r
Hi Tim ,
I am sorry that one was the outdated consumer , I have changed it long time
back and forgot to update the gist. Yes i have tried yourway but the same
result.
Thanks,
Akhil.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/JMS-exception-during-the-Failover-tp471
Hi all,
In my domain there is a cluster of 2 brokers and several CMS clients. The
failover protocol works very well when i switch off ActiveMQ on one of the
brokers, but not *when I unplug the network cable* from the server. In this
case, it takes about 10 seconds to switch to the other node, where
You are probably missing the spring and/or xbean-spring dependency
On 9/21/16 1:15 AM, TC wrote:
Hi,
After creating the network of brokers, i.e. about 4 of them on the same
laptop.
I can start them without any problem.
Not sure what I have changed in between - not it doesnt start.
Here is er
For your first question, if that happens, you'll get an overflow
exception. Of course, Long.MAX_VALUE is 9223372036854775807, so you're
worrying about a non-issue.
For your second question, can you please clarify exactly what you're
asking? Also, depending on what the question is, you may have b
To answer your first question, growing larger than Long.MAX_VALUE is
practically impossible. The value is 9,223,372,036,854,775,807. Even if
you were to create 1 temporary queue every millisecond it would take over
292 million years to reach Long.MAX_VALUE
For your second question, there is no is
Looks like maybe the core spring jar is no longer in your class path.
On Sep 21, 2016, at 7:36 AM, TC
mailto:thiam.che...@gmail.com>> wrote:
Hi,
After creating the network of brokers, i.e. about 4 of them on the same
laptop.
I can start them without any problem.
Not sure what I have changed i
First Question:
Method JmsInvokerClientInterceptor.doExecuteRequest(Session, Queue, Message)
is trying to create a TemporaryQueue then delete it. However, for each
TemporaryQueue, connection will use LongSequenceGenerator to generate a
incrementing queue name, what if sequence id grow bigger than
L
Hi,
After creating the network of brokers, i.e. about 4 of them on the same
laptop.
I can start them without any problem.
Not sure what I have changed in between - not it doesnt start.
Here is error exception - any guides on how to troubleshoot more
Loading message broker from: xbean:activ
The catch block in your consumer looks very suspicious, since it starts
additional consumers without closing the previous ones. Would you please
comment out the line that's there, and also add a line to log the exception
you're catching?
Tim
On Sep 20, 2016 11:16 AM, "akhil" wrote:
> Hi Tim ,
The most likely place for you to have old messages laying around is in the
DLQ. The next most likely place is on a topic for an offline (and never
coming back) durable subscriber.
Tim
On Sep 20, 2016 2:02 PM, "Christopher Shannon" <
christopher.l.shan...@gmail.com> wrote:
Do you have old messag
I am not having knowledge on c plus program
if anyone having Apache.NMS.AMQP.dll 32bit Windows, Can you please share the
binary files with its dependency binary files.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Can-you-please-share-Apache-NMS-AMQP-dll-tp4716686.html
You can see that the client granted 1 credit (presumably when you
called fetch) for the broker to send a message, then received a
message, granted another credit and accepted the first message, but
then didn't receive any more messages. Looks like
https://issues.apache.org/jira/browse/AMQ-6422.
On
Hi , thanks for your answer. Find below log trace from the process ..
Best regards, Javier
javier@draco $ cat log.txt
[0x7911e0]: -> AMQP
[0x7911e0]: <- AMQP
[0x7911e0]:0 -> @open(16)
[container-id="62b1050c-8b62-412c-9c68-30574005db10", channel-max=32767,
properties={:"qp
16 matches
Mail list logo