it works if you specify it on both ends,
so you have the client correct, on the server you need to specify it too
uri="tcp://localhost:61616?maxInactivityDuration=-1&jms.prefetchPolicy.all=1"
/>
Filip
fl wrote:
Hello,
I have trouble with disabling prefetch buffer for consumers. I
this is because the build tool, Maven, that is used to create the
distros for ActiveMQ, doesn't create compatible binaries for Solaris,
even if you use gtar on Solaris, as opposed to the regular one.
this is what I had to do to get it to work
1. download the .tar.gz onto a linux box
2. gunzip
Danilo Tuler wrote:
Hi Filip,
Filip Hanik - Dev Lists wrote:
in the test case provided, the program is trying to create 5000+
connections/sessions, hence that would require 5000 threads, not very
scalable.
No, the program is not creating 5000+ connections/sessions. There is a
Danilo Tuler wrote:
Hi Filip,
Filip Hanik - Dev Lists wrote:
essentially, it's more of a tuning thingy then a memory leak, if one
needs that many topics/queues, then not running with the dedicated task
runner sounds like the solution,
I didn't understand why you cla
mode on the producer) - and
then set the DLQ strategy property processNonPersistent=false
cheers,
Rob
http://open.iona.com/products/enterprise-activemq
http://rajdavies.blogspot.com/
On 20 May 2008, at 15:33, Filip Hanik - Dev Lists wrote:
Sure Badri,
our use case that we were dropping me
ion strategies". By doing this I am hoping that other fast
consumers receive data. Do you think plugin filters could also make a
difference since this is a data sensitive application?
Thanks
Badri
Filip Hanik - Dev Lists wrote:
Sure Badri,
our use case that we were dropping messages on t
mandira wrote:
We are using ActiveMQ for parallel processing - Some of parallelism achieved
through JMS Listeners and some through multiple threads.
While running the application after some time - we were always getting "Out
of Memory" Error
yeah, but what kind of OOME? there are many types
e broker plugin filter?
I also need to create policy entry for temporary topics.
Thanks for your help & time.
Badri
Filip Hanik - Dev Lists wrote:
I couldn't get that to work properly, I even tried topic="ID>" since
that was the prefix, and didn't work either.
I worked
ll topics or all queues right (since
the actually names are dynamic)?
One way to do it might be to use topic='>' since that would match all
topics (temp topics are still topics). But I guess we should have
something a little bette than that.
On Fri, May 9, 2008 at 7:45 PM, Filip
essentially, it's more of a tuning thingy then a memory leak, if one
needs that many topics/queues, then not running with the dedicated task
runner sounds like the solution,
Filip
Filip Hanik - Dev Lists wrote:
so it seems there are two OOME problems
either you hit java heap space erro
that's inside the JVM, the thread causing the crash is "VMThread".
turn off the debugger in the JVM
ie, remove the line
-agentlib:jdwp=transport=dt_socket,suspend=y,address=localhost:1679
and try again
Filip
sk123 wrote:
Hi,
I am using Active MQ 5.1. My test is to send 4000 event in a min
so it seems there are two OOME problems
either you hit java heap space error, or if you have increased your -Xmx
very high, you'll run into OOME caused by not enough mem for the number
of threads it tries to create.
the two errors are directly related to each other, increasing -Xmx (java
hea
vemq-5.2-SNAPSHOT-src.zip maven-shared-archive-resources
Filip
Bruce Snyder wrote:
On Fri, May 16, 2008 at 10:10 AM, Filip Hanik - Dev Lists
<[EMAIL PROTECTED]> wrote:
can I build a distribution without having to upload or do any SVN actions,
I'm reading
http://activemq
ld build a build without you needing to use
the release process?!?
Thanks,
Aaron
On Fri, May 16, 2008 at 12:34 PM, Aaron Mulder
<[EMAIL PROTECTED]> wrote:
Move your eclipse files away for long enough to do the build?
Thanks,
Aaron
On Fri, May 16, 2008 at 12:10 PM, Filip Han
can I build a distribution without having to upload or do any SVN actions,
I'm reading
http://activemq.apache.org/release-guide.html
also, when,
mvn release:prepare -DdryRun=true -Prelease
I get the error
Caused by: org.apache.maven.plugin.MojoFailureException: Cannot prepare
the release bec
this might not be related to the pool, but the fact that statements and
resultsets are not closed.
the error comes directly from Oracle,
Filip
Hiram Chirino wrote:
could you try using the C3P0 [1] connection pooling instead of the
default commons logging pooling. Some folks have reported bet
you have two options
1. the java service wrapper runs on unix too, you can get the wrapper
itself from
http://wrapper.tanukisoftware.org
2. just write your own shell scripts to manage start/stop of the
activeMQ program, this is a fairly trivial exercise on unix systems
Filip
Michael Caplan
d the failover transport and enable async send and dispatch
we are not seeing this issue anymore atleast not so far...
good!
Thanks again for taking time to respond!
you're welcome
Filip
Filip Hanik - Dev Lists wrote:
at
org.apache.activemq.ActiveMQConnection.sync
from the server
when taking thread dumps, always take two of them, otherwise you don't have a reference in time
Filip
jaya_srini wrote:
here's the link
http://www.nabble.com/file/p17221085/thread_dump.txt
thanks
Jaya
Filip Hanik - Dev Lists wrote:
paste it into the
paste it into the email or provide a link to it,
attachment dont make it to the user list
Filip
jaya_srini wrote:
Hi Filip
I have attached the file "thread_dump.txt" that gives the thread-dump.
if you need more info please let me know.
thanks!
jaya
Filip Hanik - Dev Lists wrot
eProducerSupport.send(ActiveMQMessageProducerSupport.java:268)
at
org.apache.activemq.ActiveMQTopicPublisher.publish(ActiveMQTopicPublisher.java:146)
Filip Hanik - Dev Lists wrote:
as I mentioned, the blocking happens on the mutex for an
ActiveMQSession, the only way you can end up block
-0700, Filip Hanik - Dev Lists wrote:
using gunzip and tar on solaris and windows(gunzip and tar ports) I get
the following
x apache-activemq-5.1.0/webapps/fileserver/WEB-INF/web.xml, 1860 bytes,
4 tape blocks
tar: ././@LongLink: typeflag 'L' not recognized, converting to
using gunzip and tar on solaris and windows(gunzip and tar ports) I get
the following
x apache-activemq-5.1.0/webapps/fileserver/WEB-INF/web.xml, 1860 bytes,
4 tape blocks
tar: ././@LongLink: typeflag 'L' not recognized, converting to regular file
x ././@LongLink, 108 bytes, 1 tape blocks
x
a
Rob Davies wrote:
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
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
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
below are
for the broker.
Michele
On 2 May 2008, at 00:20, Filip Hanik - Dev Lists wrote:
-Xms512m -Xmx1024m -Xmn500m
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
got it, BrokerPlugin
Filip
Filip Hanik - Dev Lists wrote:
I'm having a hard time figuring out how to configure a custom broker
filter,
where in activemq.xml do I configure this?
Filip
I'm having a hard time figuring out how to configure a custom broker filter,
where in activemq.xml do I configure this?
Filip
is there a way to create a
for temporary topics?
Filip
ame rate as being produced. I have 4 producers that are also consumers.
Currently the consumers when they receive the message just log it to a log
file.
Filip Hanik - Dev Lists wrote:
that means youre producing messages faster than they are being consumed.
you could setup a policy entry to t
that means youre producing messages faster than they are being consumed.
you could setup a policy entry to turn off flow control
memoryLimit="10mb"/>
memoryLimit="10mb"/>
however, if your consumers never catch up, then you need to decide what
you wanna do with your messages, as eventually y
hi,
I have two questions about policy entries and wild card matching,
can I configure my entries like this
memoryLimit="10mb">
Questions:
1. is the matching ordered, ie, if I match on the first entry, those
settings apply, and then fallback to the second?
2. Do these policy entr
rvices/training/webinars.html
it's recorded, and you'll learn how java memory management works
Filip
Michele
On Thu, May 1, 2008 at 7:50 PM, Filip Hanik - Dev Lists
<[EMAIL PROTECTED]> wrote:
when it happens, do a thread dump to make sure you don't have a thread leak
when it happens, do a thread dump to make sure you don't have a thread
leak (too many threads)
then lower your -Xmx setting, this will make more room in the JVM for
threads,
Filip
Michele Mazzucco wrote:
Hi all,
I'm facing the following error while using AMQ 5.0
ERROR efaultMessageListene
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 an OOME
we have this setting
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 an OOME
we have this setting on the server
memoryLimit="10mb">
if you look at the message
java.lang.OutOfMemoryError: unable to create new native thread
this will tell you that it has nothing to do with your Xmx setting.
Threads and thread stacks are allocated outside your Java heap (ie, your Xms and Xmx settings)
and you've simply run out of space to cre
40 matches
Mail list logo
