Using activemq 5.4.0 for a P2P desktop applicaiton, I get an OOME when
my computer awakes from sleep:
Exception in thread "InactivityMonitor WriteCheck"
java.lang.OutOfMemoryError: unable to create new native thread
The cause appears to be:
- WRITE_CHECK_TIMER schedules checks at a fixed rate
I recently did perf measurements using activemq. You can find the results and
configs here
http://www.liquid-reality.de/pages/viewpage.action?pageId=5865562
For simple one way pure jms i got about 5500 messages/s
Christian
Von meinem iPhone gesendet
Am 12.07.2011 um 00:55 schrieb MaryAuaun :
Sorry for the wrong message..
What is actually happened is, i was polling the queue while browsing...
So i get same message again and again in the browser...
Error code;
browser = session.createBrowser((Queue) destination);
Enumeration enumeration = browser.getEnumeration();
if (enume
Hi,
can you test the latest release 5.5.0 (or the latest 5.6-SNAPSHOT) and
confirm that problem still exists?
Regards
--
Dejan Bosanac - http://twitter.com/dejanb
-
The experts in open source integration and messaging - http://fusesource.com
ActiveMQ in Action - http://www.mannin
Hi,
I have the following setup:
- ActiveMQ 5.3.2
- Pure Master/Slave
- ~800 consumers
- ~320 queues
- ~650 topics
My monitoring shows that the memory usage is going up daily, in 5 days
the heap used went up by 50MB without any changes in consumers, queues
or topics count. I tried to force GC but
Actualy I found from where the error comes :
The JNDI lookup to Weblogic return a weblogic.jms.common.DestinationImpl
instance that is the Weblogic generic implementation for Queue and Topic.
In the org.apache.activemq.command.ActiveMQDestination class the transform()
method can obtain both a que
Thanks Dejan, That's very helpful!
-Mark
On Wed, Jul 13, 2011 at 3:30 AM, Dejan Bosanac wrote:
> Hi Mark,
>
> the message by default is sent in serial order to all available
> subscribers.
> It can be changed by implementing appropriate DispatchPolicy
>
>
> https://fisheye6.atlassian.com/brow
Thanks Gary. I can confirm that sending with transactions works perfectly but
slower than AUTO for my scenario where messages are generated one by one and
need to be sent one by one.
What are the disadvantages of disabling audit in kahadb (apart from the
obvious - duplicates won't be suppressed)?
that is a problem, if broker death occurs between the first send to a
composite destination and the last send (all of which occur on the
broker), the resend will be suppressed but there is no guarantee that
each of the composite dests got the message.
The duplicate suppression is not aware of comp
Thanks Gary.
I've tested below with Fuse 5.5 (apache-activemq-5.5.0-fuse-00-27) and
unfortunately the issue is there. However what it boils down to is this
"suppressing duplicate message send" message in composite destinations.
In order to prove this is the case, I started eliminating components
There is also a very detailed tuning guide from FuseSource here (need to
register first):
http://fusesource.com/require_registration_for?url=http://fusesource.com/docs/broker/5.5/tuning/tuning.pdf
Ozan
-Original Message-
From: mickhayes [mailto:mickha...@gmail.com]
Sent: 12 July 2011 0
Can you create a test case that reproduces it?
Regards
--
Dejan Bosanac - http://twitter.com/dejanb
-
The experts in open source integration and messaging - http://fusesource.com
ActiveMQ in Action - http://www.manning.com/snyder/
Blog - http://www.nighttale.net
On Wed, Jul 13,
Hi Mark,
the message by default is sent in serial order to all available subscribers.
It can be changed by implementing appropriate DispatchPolicy
https://fisheye6.atlassian.com/browse/activemq/trunk/activemq-core/src/main/java/org/apache/activemq/broker/region/policy/DispatchPolicy.java?hb=true
13 matches
Mail list logo
