Again I have to reply myself to provide more information...
It seems from my tests that even the socket.tcpNoDelay=true flag has an
effect on broker configuration (in activemq.xml file). It only seems to work
in client connection URIs. The other 2 possibilities (tcpNoDelay=true and
wireFormat.tcp
Op woensdag 21 februari 2007 21:05, schreef eccrowe:
> It should also be noted that after a client power off, the remaining active
> clients very quickly stop receiving their messages. Server logs still
> appear to be sending messages but the enqueue count is not increasing in
> the jmx-console a
Hi
We tried building activemq-cpp latest source code on linux
Linux 2.4.21-37.ELsmp #1 SMP Wed Sep 7 13:28:55 EDT 2005 i686 i686 i386
GNU/Linux
Here is the error that we got for it
checking for Cppunit - version >= 1.10.2... 1.10.2
checking for pthread_create in -lpthread... no
confi
We recently migrated our application from ActiveMQ3.2.1 to ActiveMQ 4.1.0.
We were using a listener for Expired messages (after timetolive) when we
used ActiveMQ 3.2.1 using DeadLetterPolicy class.
When we switched to ActiveMQ 4.1, we noticed that the DeadLetterPolicy class
has been changed in 4
GaryG wrote:
> AMQ Broker is down again. Same situation. However, running "jstack" on the
> PID doesn't work, it hangs connecting to the process.
>
> So, I opened up the JMX console, and am providing you some of stats that
> looked interesting.
>
> My main questions regarding this output are:
>
AMQ Broker is down again. Same situation. However, running "jstack" on the
PID doesn't work, it hangs connecting to the process.
So, I opened up the JMX console, and am providing you some of stats that
looked interesting.
My main questions regarding this output are:
1) Why does Broker memory
I would like to know if the filters can be used for virtual topic so only
needed messages are delivered to the physical queues that are tied to the
virtual topic.
Thanks!
--
View this message in context:
http://www.nabble.com/Can-Filters-be-used-for-virtual-topic-tf3269702s2354.html#a9090514
Sen
On 2/21/07, GaryG <[EMAIL PROTECTED]> wrote:
I was wondering if anyone knows of consultants (consulting companies) that
might specialize in ActiveMQ services. I'd like to have the info handy if
we ever need to bring someone in to help us solve issues and tune.
LogicBlaze provides services an
I am testing failover scenarios with ActiveMq 4.1 and with Shared File System
Master Slave. The failover seems to work fine - but I notice that some
messages remain "stuck" in the queue after the failover and don't get
consumed. If I restart the consumer application after the failover happens
then
I was wondering if anyone knows of consultants (consulting companies) that
might specialize in ActiveMQ services. I'd like to have the info handy if
we ever need to bring someone in to help us solve issues and tune.
Thanks.
--
View this message in context:
http://www.nabble.com/ActiveMQ-consu
Chris, in this specific case we're using Topics, not Queues, but I've seen
the same issue happen for Queues. Next time it "hangs" I'll get a stack
dump and post it. Should be sometime this evening (I've not seen it run
reliably for more then 8 hours)
Thank you.
_Gary
Christopher G. Stach II
GaryG wrote:
> I've got the JMX running. Again the architecture ran fine for about 3 hours,
> then all my topics seemed to stop receiving messages.
>
> So, here's the situation:
>
> 1) the producers ARE sending messages and there are no exception from AMQ
> API when they're sent.
> 2) AMQ Brok
I've got the JMX running. Again the architecture ran fine for about 3 hours,
then all my topics seemed to stop receiving messages.
So, here's the situation:
1) the producers ARE sending messages and there are no exception from AMQ
API when they're sent.
2) AMQ Broker is up, and amq logs indic
Have deployed 4.1.0 and it appears that things have at least initially not
improved. I am no longer seeing any increase in memory but I am also now
not seeing any consumer removal when the client has been powered off. This
is apparent when examining the jmx console and the activemq server DEBUG
Hi,
Does anyone know if https://issues.apache.org/activemq/browse/AMQ-765 is
fixed? I've looked at the source code and I can't see any references to
transient variables now...perhaps it is fixed?
-=david=-
--
View this message in context:
http://www.nabble.com/ActiveMQ-and-Glassfish-tf3267635s
I have not looked at the JMX stats. For whatever reason, I haven't been able
to connect remotely to the broker.
Aside from that...Why would a broker kill clients due to inactivity? Can
this be configured/turned off?
In our case, the producers of messages to this topic are sending messages
ever
16 matches
Mail list logo