On 12 May 2008, at 19:28, Filip Hanik - Dev Lists wrote:
I am publishing to a temporary topic, producing fast, consuming slow
after a while the memory usage kicks in on the server.
if I disconnect the consumer/producer (ie, kill the client) the
server remains stuck in this state, and nothing
as I mentioned, the blocking happens on the mutex for an
ActiveMQSession, the only way you can end up blocking two threads there,
is if two threads are using the same session,
can you post the complete thread dump?
thanks
Filip
jaya_srini wrote:
So Sorry! :(
I just thought I would explain o
So Sorry! :(
I just thought I would explain our scenario in more details.
jaya_srini wrote:
>
> Hello
>
> Apologies for all the questions but I am a newbie to ActiveMQ and I would
> really like to better understand how the ActiveMQ broker works and was
> wondering if someone can explain how i
is this the same issue as you posted in:
*http://tinyurl.com/67yanp*
or for full URL:
http://activemq.markmail.org/search/?q=jaya_srini#query:jaya_srini%20from%3A%22jaya_srini%22+page:2+mid:ad2dkiy64bi5oejs+state:results
if so, creating multiple postings for the same issue, will actually
lessen
Filip Hanik - Dev Lists wrote:
Rob Davies wrote:
On 1 May 2008, at 00:02, Filip Hanik - Dev Lists wrote:
There doesnt seem to be a way of limiting how messages are delivered
to the client.
the ActiveMQMessageConsumer.unconsumedMessages seems to fill up, all
to quickly, and eventually cause a
seven_ephors schrieb:
I try to send a large file off band using BlobMessage, but can't get it to
work. Searched on the site, and found that some people was not able to get
it to work either. Some of them says it does not work with InputStream,
while some of them says I need to get the source co
I'm talking about the mem settings for the JVM that gets the OOME
in the settings below, I would remove the -Xmn flag, and let the JVM
size the new generation itself
Also, lower -Xmx800m, and if there is a heap space OOME problem, that
will occur before the "unable to create new native thread",
We identified what was causing the problem. One of our consumers had an
uncaught exception that was occasionally thrown in the MessageListener
thread. By simply preventing this exception we no longer see the broker lock
ups.
Is this expected consumer behavior? It seems that the broker/server shou
Thanks Rob.
rajdavies wrote:
>
>
> On 8 May 2008, at 22:15, Badri wrote:
>
>>
>> Hi
>>
>> I read about slow consumer from this URL:
>> http://activemq.apache.org/slow-consumers.html
>> Non-Durable Topics
>>
>> Non-durable topics are the scenario which is most affected by slow
>> consumers
I am publishing to a temporary topic, producing fast, consuming slow
after a while the memory usage kicks in on the server.
if I disconnect the consumer/producer (ie, kill the client) the server
remains stuck in this state, and nothing gets cleaned up, and the server
is unusable.
Is this a kn
I try to send a large file off band using BlobMessage, but can't get it to
work. Searched on the site, and found that some people was not able to get
it to work either. Some of them says it does not work with InputStream,
while some of them says I need to get the source code and compile the
proj
Is it possible to do this with the current version of Activemq with tomcat?
Any suggestion is highly appreciated. Thanks.
On Thu, May 8, 2008 at 10:21 AM, sudip shrestha <[EMAIL PROTECTED]> wrote:
> Is it possible to setup jndi with ssl connection for Activemq in tomcat.
> If so where do I define
Hi ,
I am doing some performance testing for our project requirement.
we will have number of producer producing the message of various
sizes(1kb,10kb,16kb,512kn or even 1 mb).
Now when the consumer is not running we will persist those data's in mysql
data base which is configured with activem
On 8 May 2008, at 22:15, Badri wrote:
Hi
I read about slow consumer from this URL:
http://activemq.apache.org/slow-consumers.html
Non-Durable Topics
Non-durable topics are the scenario which is most affected by slow
consumers
since the messages are not persistent and messages generally go
On 8 May 2008, at 22:02, BlueFox wrote:
I just did some more checking, turns out it is the QueueBrowser that
is
causing the duplicate message problem. I have a QueueBrowser that
uses the
following code to periodically verify the queue size and perform
verification after queue size is zero
On 9 May 2008, at 10:35, Steven Van Loon wrote:
Hi,
Does anybody knows whether and how it is possible to act on expired
messages?
Thanks!
Steven.
Expired messages have taken too long to deliver to a consumer - they
are sent to a dead letter queue - see http://activemq.apache.org/mes
16 matches
Mail list logo