These accumulate (are not auto-purged) when they still contain undelivered
messages to at least one registered subscriber. Check that all subscribers
are acknowledging receipt of all messages. Also check that your message
expiration times are set to a reasonably short period of time.
Mark
On
OK. The client app has a durable consumer C has connected to Topic T, and
while it is active, messages X, Y, and Z are eventually delivered by the
broker and consumed by C. Then, C disconnects and then reconnects
(sometimes immediately). When C reconnects, sometimes messages X, Y, and Z
are
I'm reposting this with updated information.I'm setup to use durable Topics
with retroactive=true. My application consumes messages, which lights up
certain status indicators. While this works fine, I have a problem in that
if the user exits and restarts my application, sometimes the messages
Yeah, I knew I was forgetting something. I have the message delivery setup
as a durable Topic with retroactive set to true.
Mark
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Redelivery-of-messages-already-consumed-tp4721576p4721578.html
Sent from the ActiveMQ - User
My application consumes messages, which light up certain status indicators.
While this works fine, I have a problem in that if the user exits and
restarts my application, sometimes the messages are redelivered and
sometimes they are not. I want all non-expired messages to be redelivered
upon
I have a connection ID like this:
ID:fantastic-42428-1411556345970-7:1
What I know so far is: fantastic is the client hostname; 42428 is a random
number from 0 to 65535 and has no meaning; 1411556345970 is the timestamp of
the connection (seconds since 00z 1/1/1970).
What I don't know is what
I wrote 3 Java apps whose GUIs update upon receiving messages from AMQ.
While AMQ runs 24/7/365, my apps only run for as long as the user's shift
lasts (up to 10 hours). However, after AMQ is running for about 4 days, one
(or more) of these three apps seems to lose its ability to receive
offlineDurableSubscriberTaskSchedule
http://activemq.apache.org/manage-durable-subscribers.html
On Fri, Jun 28, 2013 at 12:06 PM, fenbers lt; [hidden email] gt;
wrote:
gt; Greetings!
gt
Greetings!
I want ActiveMQ to automatically cleanup (unsubscribe) idle subscribers who
haven't connected in, say, 3 days. I couldn't find this in the
documentation. Is this possible? And if so, what configuration option is
it?
Mark
--
View this message in context:
Due to ongoing network issues, we find it necessary to reboot ActiveMQ
occasionally. Previously, clients had to be started as well to reestablish
a connection with the newly rebooted broker. So now I implemented the
failover feature so that the clients can automatically reconnect with the
broker
I get an eror on AMQ startup that I request 1gb of temporary store limit but
only 500mb are available on ${activemq_home}/data/localhost/tmp_storage
I read many googled pages, but found nothing on how to change the location
of this storage. Does anyone know?
--
View this message in context:
, fenbers lt; [hidden email] gt;
wrote:
gt;
gt;gt;
gt;gt;
gt;gt;
gt;gt;
gt;gt;
gt;gt; nbsp; nbsp;I'm getting the Sync exception on both, local and
NFS.amp;nbsp;
gt;gt; Originally,
gt;gt
If ActiveMQ is restarted, we find that our producers and our consumers have
to be shut down and relaunched in order to reestablish the connection with
ActiveMQ. This is a royal pain! However, a producer will throw an
exception whenever it tries to send a message through a lost connection, and
so
I'm getting the error shown in the Subject, not at first, but after ActiveMQ
has been working just fine for several hours. Then once it happens, all my
clients that interact with the broker reports this error. I've found this
page:
making it across the network to the broker,
or that
the broker's info is making it back to the client? or getting
blocked
somehow?
On Mon, May 13, 2013 at 10:50 AM, fenbers lt; [hidden email] gt;
wrote
Thanks!nbsp; I'm studying up on tcpdump's man page now (about 30 pages
of technical details!).nbsp; Wireshark isn't installed by default, so I
put in a request to have it installed on Tuesday.nbsp; I won't be back
in until Thursday, so I'll resume my diagnostics
OK, here's some useful info...nbsp; I used:
nbsp;nbsp;nbsp; tcpdump tcp port 61616 and host dell7
I noticed that if I use:
nbsp;?wireFormat.maxInactivityDurationInitialDelay=3
in my client to extend the timeout to 30 seconds instead of the
Here is the second log fro May 3 with a different error/stacktrace at
08:00:02,028, but is one mentioned to be fixed in AMQ-4118... This error
did not trigger a self-shutdown of ActiveMQ, but ActiveMQ clients did cease
receiving messages from this broker. Thus, from a client perspective,
Zagan wrote
Can you please check if your .log files in the /data directory are cleaned
up? On basis of the information I suppose this behaviour is due to a
misconfiguration of your clients.
If this is the case often broken log file cleanup is a symptom.
I get the same error as brought up in
Regarding https://issues.apache.org/jira/browse/AMQ-4118, the report says
this issue is fixed in 5.8.0, but I am running 5.8.0 and still have exactly
the same 3 stack traces as listed in the URL above. Moreover, I have
numbered .log files (journal files) that never get cleaned up automatically.
/browse/activemq/trunk/activemq-core/src/test/java/org/apache/activemq/usecases/DurableSubsOfflineSelectorConcurrentConsumeIndexUseTest.java?r=1400317
On Tue, Apr 30, 2013 at 9:02 AM, fenbers lt; [hidden email] gt;
wrote:
gt; Regarding https
and
resubmit these messages to the broker if necessary?)
Torsten Mielke
[hidden email]
[hidden email]
nbsp;
On Aug 9, 2012, at 8:17 PM, fenbers wrote:
gt
My ActiveMQ broker instance is configured for a recovery policy to allow
messages (up to 6 minutes old) to be resent even after acknowledgement. If
the client app is restarted, it will receive redelivered messages (if they
were brokered within the past 6 minutes). This works great, except for
of
using the broker as a DB:
http://sensatic.net/messaging/messaging-anti-patterns-part-1.html .
Hope that helps,
Raúl Kripalani.
On 9 Aug 2012, at 23:07, fenbers lt; [hidden email] gt;
wrote:
gt
://about.me/raulkripalani
lt; http://twitter.com/fusenews gt;
On 7 August 2012 13:47, fenbers lt; [hidden email] gt;
wrote:
gt; I've configured my ActiveMQ client not to acknowledge
messages. This is
gt; because I
Yes, your suggestion works, and you *are* an angel!! I have just one simple
follow-up question. I have one ActiveMQ instance brokering two separate
topics. I want to set one topic (with many large messages) with a
timedSubscriptionRecoveryPolicy of 6 minutes, while the other topic has much
Greetings!
I want unexpired JMS messages to be redelivered if my client application is
stopped and restarted. To accomplish this, I do not have the client
acknowledge the receipt of messages. An unfortunate side-effect of this
practice is that the db-/N/.log files in the ${activemq.data}/kahadb
Is there a way for my client app to request redelivery of unexpired messages
that my client has already acknowledged in a previous instance?
Session.recover() will only resend un-acknowledged messages.
Mark
--
View this message in context:
I've configured my ActiveMQ client not to acknowledge messages. This is
because I want the messages redelivered if the user stops and restarts the
client app. The messages expire in 6 minutes anyway. So any older messages
*shouldn't* be delivered.
I notice in my $ACTIVEMQ_HOME/data/kahadb
The AMQ log shows lots of stuff (33MB in about 6 hours) but most of it
comprises of this error:
-MM-DD HH:MM:SS,ddd | WARN | Duplicate message add attempt rejected.
Message id: myhostname-59695-1291947282050-0:1:1:1:513 |
org.apache.activemq.store.kahadb.MessageDatabase | ActiveMQ Transport:
are set to
expire at less than 12 from the current time, so it's not like message
are kept for long periods of time.
Mark
begin:vcard
fn:Mark Fenbers
n:Fenbers;Mark
org:National Weather Service;Ohio River Forecast Center
adr:;;1901 South OH-134;Wilmington;OH;45177-1908;USA
email
begin:vcard
fn:Mark Fenbers
n:Fenbers;Mark
org:National Weather Service;Ohio River Forecast Center
adr:;;1901 South OH-134;Wilmington;OH;45177-1908;USA
email;internet:mark.fenb...@noaa.gov
title:Sr. HAS Meteorologist
tel;work:937-383-0430
tel;fax:937-383-0033
note:HAS is an acronym for Hydrometeorological
Hi,
My AMQ clients get very slow or freeze up altogether after about 30 days of
ActiveMQ running. I solve the problem (until about 30 days later) by
deleting the $ACTIVEMQ_HOME/data/kahadb directory and restarting ActiveMQ.
In looking for clues to this problem, I notice (before I delete the
But wouldn't consuming them just take them out of the queue for the current
application/consumer? Wouldn't the messages still linger on AMQ for all the
other clients?
Mark
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Change-Expiration-tp3072602p3074720.html
Sent from
Greetings,
My client app creates a message with a 12-hour expiration and sends the
message to the broker. But later, from another client app, I want to
revise the expiration of the original message. Is this possible?
Or, if not possible, or too complicated, another option would be to
35 matches
Mail list logo
