Hi,
I am using activemq-cpp-3.9.3. I want to set ttl value on a producer or
while sending messages.
The moment I set ttl value using producer->setTimeToLive(3), the
messages never delivered to the broker. If I comment above line all is fine
and messages are delivered properly. Can anyone help m
Hi Guys
I am running Broker using: 'java -cp activemq-all-5.14.1.jar
org.apache.activemq.console.command.ShellCommand start' (JDK8u60).
Besides of this I used OpenWire example code for Java:
https://www.dropbox.com/s/y654vrltof1w0p2/openwire2.zip?dl=0
I have just modified Producer's code to send
How do you know they aren't delivered to the broker?
Have you checked that the clocks on the machines are in sync?
On 10/20/2016 08:27 AM, mkoppala wrote:
Hi,
I am using activemq-cpp-3.9.3. I want to set ttl value on a producer or
while sending messages.
The moment I set ttl value using producer
I check in broker uri and also capture the trace on broker port.
The clocks are in synch.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/activemq-cms-timeToLive-is-creating-an-issue-tp4718128p4718133.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
If you want someone to offer you help then it'd be good to cover what
you've done to analyze the problem.
On 10/20/2016 09:27 AM, mkoppala wrote:
I check in broker uri and also capture the trace on broker port.
The clocks are in synch.
--
View this message in context:
http://activemq.228332
Great. Good to hear.
On Wed, Oct 19, 2016 at 2:58 PM, hcrobison
wrote:
> I am all set. My problem was when we embedded the Artemis server, we missed
> the jar arttemis-hornetq-protocol-1.x.0.jar.
> Thanks.
>
>
>
> --
> View this message in context: http://activemq.2283324.n4.
> nabble.com/Horne
Sorry for less information.
I tried the following:-
Just now I changed the delivery mode to PERSISTENT and setting the ttl. The
messages are getting delivered to the broker now.
But still I see the messages are not discarded at broker after the timer
expiry.
I suppose the api call to setTimeToLiv
As far as I know there haven't been any reports or issues having to do with
a memory leak in recent versions.
How much memory is being used is really up to the JVM in terms of how it
handles allocation and GC. The only way to really know if there is a
memory leak is to analyze the results of a he
the JMS layer on Artemis is a thin layer on top of the Core API. I
would stick to JMS or JMS2.
There are some extra controls you can have on addresses and queues but
that will soon also come into JMS after martyn is done with the
refactoring on addressing here:
https://github.com/apache/activemq-
Take a look on QueueControl::browse
It would be easy to patch it to look at the ScheduledDeliveries. I
could even guide you around it if you are interested.
On Tue, Oct 18, 2016 at 2:36 PM, abhijith wrote:
> I am assuming you are referring to JMSBrowser.
>
> We have locked down Queues and Top
when you have the same subscription created among different boxes, it
will follow the LOAD_BALANCE policy you have selected.
When it's different subscriptions, all the boxes on the same cluster
connection will receive the same messages. i.e. it will distribute to
them all.
On Fri, Oct 7, 2016
11 matches
Mail list logo