Hi
using Activemq v5.8
We create a queue, delete it through the jconsole, and attempt to recreate
it, receiving the error below on the client. But when filteredKahaDB
perDestination is disabled, queues can be deleted and recreated without
issues.
I have already gone through https://issues.apache
Final test.
I reproduced this in CentOS 6.0 under Java "1.7.0_09-icedtea" and a clean
ActiveMQ 5.9.0 install.
Same steps as before. I issued a Terminate jvm(int) or Stop() command from
Hawtio console to trigger the same behaviour.
I don't get this problem when sending "activemq stop" from from
I was able to reproduce the problem and get a stack trace for the hanging
thread. It appears to be waiting for data from the ActiveMQ broker.
#0 0xb76f4424 in __kernel_vsyscall ()
#1 0xb76e09db in read () from /lib/i386-linux-gnu/libpthread.so.0
#2 0xb6bee435 in read (__nbytes=, __buf=0xb600583
what kind of restriction do you mean ?
On Wed, Mar 12, 2014 at 5:33 PM, khandelwalanuj wrote:
> Hi,
>
> Using ActiveMQ v.5.8
>
> I want to know that is there a way to restrict a perticular client to
> connect to the broker ?
>
> I am using my own plugin where I override addConnection function,
We have ActiveMQ 5.2.0 and use its admin UI. When we access the UI, the
cookie set by the server is not secure one, that is that httponly flag is
not set in the cookie.
Can someone tell me how to solve this problem?
Thank you very much!
--
View this message in context:
http://activemq.228332
sorry, i miss read "client side ack", it is not needed.
On 13 March 2014 16:47, davery wrote:
> No, I didn't think that was required when the session is in auto
> acknowledgement mode.
>
> From: gtully [via ActiveMQ] [mailto:ml-node+s2283324n4679023...@n4.nabble.com]
> Sent: Thursday, March 13,
Hi
I'm having info and error log messages when my consumer get messages. Im
not sure it it happens cause my cluster of brokers are duplicating due to
"Store and forward".
my-broker-4
2014-03-13 10:44:09,832 | INFO | my-broker-4 Ignoring sub from
my-broker-2, browsers explicitly suppressed |
org
Hi,
using : ActiveMQ 5.8
I am looking into jconsole for a queue subscribers. Can you please tell me
difference between following terms:
*1. MessageCountAwaitingAcknowledge
2. PendingQueueSize
3. MaximumPendingMessageLimit
4. PrefetchSize*
--
View this message in context:
http://activemq.2283
No, I didn't think that was required when the session is in auto
acknowledgement mode.
From: gtully [via ActiveMQ] [mailto:ml-node+s2283324n4679023...@n4.nabble.com]
Sent: Thursday, March 13, 2014 9:41 AM
To: Avery, Dave
Subject: Re: ActiveMQ consumers stop accepting messages
and the app does me
Hi,
ActiveMQ version: 5.8
I am talking about the case of slow consumer (consumer is not able to
consume those msgs).
when prefetch limit is exceeded this thing happens.
In this case: In case of topics (both durable and non durable subscription)
Do we have any strategy where we can purge or de
and the app does message.acknowledge() every now and then?
On 13 March 2014 15:52, davery wrote:
> Client side ack is set to auto acknowledge
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/ActiveMQ-consumers-stop-accepting-messages-tp4678923p4679008.html
> Sen
Hi,
Version: 5.8
If I am sending persistent messages on a queue and no consumer is running,
broker will store all those msgs in kahadb. Now if I purge the queue, borker
will delete all the messages on that queue ? Will it also delete messages
from kahaDB ?
Thanks,
Anuj
--
View this message in
Client side ack is set to auto acknowledge
--
View this message in context:
http://activemq.2283324.n4.nabble.com/ActiveMQ-consumers-stop-accepting-messages-tp4678923p4679008.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
The code in question is part of unmarshalling - which means data coming in
must be properly interpreted. It's possible the incoming stream is
misinterpreted with the older library and that's corrected.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/activemq-cpp-3-7-0-cr
Hmm, a segfault in std::basic_string points to something troubling. Two
ideas coming to mind - the library is not being initialized properly, or
there is corruption earlier (probably due to pointer problems) that's
causing this later call to fail.
In the case of initialization not being correct -
Sorry for the late response. I know we have a special sort of scenario, but
maybe you can help us. I did some debugging, here are some informations:
Program terminated with signal 11, Segmentation fault.
#0 0x03fffb2fa2d4 in std::basic_string,
std::allocator >::basic_string() () from /usr/lib
On 03/13/2014 02:00 AM, wujianjin wrote:
thank you for you relay very much. I check the code in 3.8.2. BooleanStream
class source code didn't have any change. Does the caller of the
BooleanStream deal with the siutuation of the vector of data will not be
empty?
--
View this message in context:
Looks like consumers don't ack. What is the client side ack mode?
On 12 Mar 2014 23:11, "davery" wrote:
> Hi,
>
> I have two ActiveMQ 5.8 instances setup in a network of brokers. Each
> instance is hosted on a separate machine running Ubuntu 12.04 with 8GB of
> memory. After one week in productio
That was helpful.
One more thing:
Is there a way to kill or remove connection of a consumer/producer
connecting to a topic/queue from jconsole ? (For example we can destroy
durable subscription. )
Thanks,
Anuj
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Issue-with-
Hi
This is working correctly.
See
http://activemq.apache.org/how-do-i-find-the-size-of-a-queue.html
On Thu, Mar 13, 2014 at 8:01 AM, khandelwalanuj
wrote:
> Hi,
>
> I am using amqV5.8. What is the exact meaning of queue purging for ActiveMQ.
> According to documentation "purge a queue menas del
Hi,
I am using amqV5.8. What is the exact meaning of queue purging for ActiveMQ.
According to documentation "purge a queue menas delete all the messages on
it"
But when I purge a queue and check Jconsole, it delete all the pending
messages and consider them as dequeued.
*Before purging:
*Enqueu
21 matches
Mail list logo
