Hi,
I am using ActiveMQ v5.8 and seeing the below error continuously in broker
log file:
[20140108 06:30:01.038 EST (ActiveMQ Transport: tcp:///*.*.*.*:45678@61616)
org.apache.activemq.broker.TransportConnection#processAddConnection 772
WARN] - Failed to add Connection ID:host-34810
Hi all,
I am using the cms activemq library, in my porjet, and I have the following
problem:
under windows my own library has 3 Mo size
And on the linux os, the size growing up at 14 Mo, so why ? and how have the
minus library size ?
using the strip command to remove all debug symbols from the
On 01/08/2014 09:16 AM, MillieretXavier wrote:
Hi all,
I am using the cms activemq library, in my porjet, and I have the following
problem:
under windows my own library has 3 Mo size
And on the linux os, the size growing up at 14 Mo, so why ? and how have the
minus library size ?
using the
most if not all of that info is available already.
dlqDeliveryFailureCause property
org.apache.activemq.command.Message#getOriginalDestination (currently
not visible via a property)
org.apache.activemq.command.Message#getBrokerInTime
(System.currentTimeMillis()) via property
in broker
log file:
[20140108 06:30:01.038 EST (ActiveMQ Transport: tcp:///*.*.*.*:45678@61616)
org.apache.activemq.broker.TransportConnection#processAddConnection 772
WARN] - Failed to add Connection ID:host-34810-1389180458930-0:1, reason:
javax.jms.InvalidClientIDException: Broker
the stats are kept for as long as the broker has been up. so for the
life of the broker, would you say you haven't had messages sitting
around on a queue for 15s or greater?
On Tue, Jan 7, 2014 at 3:55 PM, uromahn ulr...@ulrichromahn.net wrote:
I've got a simple question with a hopefully simple
Wanna post your configs and test scripts?
On Tue, Jan 7, 2014 at 3:04 PM, uromahn ulr...@ulrichromahn.net wrote:
The AMQP client does not use asynchronous communication with the server. This
is embedded in the AMQP protocol, so the client sends the message and the
call to send(msg) only
nothing stands out immediately.. maybe you can complete the test case
by showing where the producer sends to the queue so that we know there
is indeed a message in the queue...
On Mon, Jan 6, 2014 at 4:52 PM, rrazey robert.ra...@dynacrongroup.com wrote:
I'm having an issue with consuming
There really isn't a good explanation for that as far as I can tell.
The regular Topic Subs make a call back to the destination... but as
Art explained, the dequeue count on a topic is not very meaningful...
the important enqueue/inflight/dequeue counts are on the
subscription... might be worth
You might want to tone down the refresh rate on the Preferences page to see
if that helps?
On 8 January 2014 17:37, Christian Posta christian.po...@gmail.com wrote:
i haven't noticed anything like this.
what OS/browser are you using?
On Sun, Jan 5, 2014 at 9:41 PM, kraythe kray...@gmail.com
Good point... verify the same numbers you see in hawtio are the same
you see in jconsole.
As for your assumption... the enqueue time is the time spent in the
broker from when the broker saw the send to when the broker
dispatches to a consumer
On Wed, Jan 8, 2014 at 9:49 AM, James Strachan
Is there a need to couple the connection's transport listener to the spring
DMLC?
It should be easy enough to create a connection listener and attach it to
the connections via the connection factory. See the setTransportListener()
method of the ActiveMQConnectionFactory. Note that if you use
That's very odd, and a challenging one to tackle.
I would check a few things. First, double-check the connections listed in
the broker are for the client in-question. Most likely they are.
Second, check the open sockets on both the client and server after stopping
the client to see if the
Final update: this is not a bug in the AMQP 1-0 JMS client but rather a
feature. Turns out that the AMQP client uses async publishing by default
boosting the performance but violating the delivery guarantee of persistent
messages.
However, when using the sync publishing mode, it appears that the
Thanks for the update, that's good-to-know.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Interesting-Persistent-Messaging-Performance-tp4676001p4676130.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
jconsole reports the exact same number, so no issue there.
I re-ran my tests and checking the statistics immediately after the run was
completed.The statistics make more sense now with the definition you
provided. The average enqueue time is consistent with the test - aprox.
1000ms which is the
On 8 Jan 2014, at 19:42, uromahn ulr...@ulrichromahn.net wrote:
jconsole reports the exact same number, so no issue there.
I re-ran my tests and checking the statistics immediately after the run was
completed.The statistics make more sense now with the definition you
provided. The average
Please...
Il 08/gen/2014 20:43 uromahn ulr...@ulrichromahn.net ha scritto:
jconsole reports the exact same number, so no issue there.
I re-ran my tests and checking the statistics immediately after the run was
completed.The statistics make more sense now with the definition you
provided. The
On 01/08/2014 02:51 PM, Daniele Teti wrote:
Please...
Il 08/gen/2014 20:43 uromahn ulr...@ulrichromahn.net ha scritto:
jconsole reports the exact same number, so no issue there.
I re-ran my tests and checking the statistics immediately after the run was
completed.The statistics make more
On 01/08/2014 02:32 PM, uromahn wrote:
Final update: this is not a bug in the AMQP 1-0 JMS client but rather a
feature. Turns out that the AMQP client uses async publishing by default
boosting the performance but violating the delivery guarantee of persistent
messages.
However, when using the
HI
I have trouble compiling ActiveMQ5.2...The following is the error message,
please help!
Total time: 15.239s
Please help!
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Unable-to-Compile-ActiveQ-5-2-tp4676139p4676140.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Please provide the steps you are using to compile, starting with obtaining
the 5.2 sources.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Unable-to-Compile-ActiveQ-5-2-tp4676139p4676141.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Thanks for reply christian.
Yeah it would be good if the metrics work in same way for both durable and
non-durable subscribers. It would also be nice if it was documented
somewhere in ActiveMQ docs as I couldn't find any information about this
behavior in ActiveMQ docs.
--
View this message
24 matches
Mail list logo
