Part of my problem I found was that I wrapped the parts of the JMS
library that I needed into my own library. For each endpoint I was
creating a producer AND consumer regardless if I need both or not.
This was leading to the producer/consumer eating up memory by creating
objects that I did not nee
Maybe some of the following options are relevant
http://activemq.apache.org/javalangoutofmemory.html#java.lang.OutOfMemory-SpoolingMessagestoDisk
On 28 June 2010 08:37, PatrickVB wrote:
>
> Hi,
>
> I know this thread is quite old. I'm getting the same error.
> The JVM which is sending message to
Hi,
I know this thread is quite old. I'm getting the same error.
The JVM which is sending message to the broker is getting an OOM.
I'm using 5.3.1. For message sending I use stream message.
Regards
Patrick
elihusmails wrote:
>
> I am finally getting the chance to continue testing this and
It is probably best to open a jira issue and submit a Junit test case
of your client that demonstrates the out of memory error.
2008/11/19 Elihu Smails <[EMAIL PROTECTED]>:
> I am finally getting the chance to continue testing this and am still
> getting OutOfMemory errors on the JVM that is sendi
I am finally getting the chance to continue testing this and am still
getting OutOfMemory errors on the JVM that is sending messages to the
ActiveMQ server. I have set the policy to
on the ActiveMQ server using the
latest code in the trunk.
Anyone have any more ideas on how to prevent these OutO
2008/10/14 Mark Webb <[EMAIL PROTECTED]>:
> nevermind, I thought this was a source code change
It was - on trunk
--
James
---
http://macstrac.blogspot.com/
Open Source Integration
http://fusesource.com/
nevermind, I thought this was a source code change
On Tue, Oct 14, 2008 at 1:52 PM, Mark Webb <[EMAIL PROTECTED]> wrote:
> on what branch did you check this in on? I just performed an update on the
> trunk and see no changes.
>
>
>
>
> On Tue, Oct 14, 2008 at 10:36 AM, James Strachan <[EMAIL
on what branch did you check this in on? I just performed an update on the
trunk and see no changes.
On Tue, Oct 14, 2008 at 10:36 AM, James Strachan
<[EMAIL PROTECTED]>wrote:
> 2008/10/14 Mark Webb <[EMAIL PROTECTED]>:
> > You would be my new best friend if you did :)
>
> Done! :)
>
> --
> J
2008/10/14 Mark Webb <[EMAIL PROTECTED]>:
> You would be my new best friend if you did :)
Done! :)
--
James
---
http://macstrac.blogspot.com/
Open Source Integration
http://fusesource.com/
You would be my new best friend if you did :)
In my opinion, it seems to me like this should be turned off by default and
then the option to turn it on is available. I am hitting OutOfMemory errors
after 10,000 messages, which takes about an hour for me.
On Tue, Oct 14, 2008 at 10:16 AM, James
2008/10/10 Rob Davies <[EMAIL PROTECTED]>:
> That's not a a memory leak you're seeing - that's the wacky Retroactive
> Consumer functionality - see
> http://activemq.apache.org/retroactive-consumer.html
> The default policy is FixedSizeSubscrptionRecoveryPolicy - and the default
> cache size for e
So I would see this increase in memory on the JMS sender? This seems a
little strange. I have tried ActiveMQ 5.2 and see the same problem on the
sending client application.
On Fri, Oct 10, 2008 at 2:39 AM, Rob Davies <[EMAIL PROTECTED]> wrote:
> That's not a a memory leak you're seeing - tha
That's not a a memory leak you're seeing - that's the wacky
Retroactive Consumer functionality - see http://activemq.apache.org/retroactive-consumer.html
The default policy is FixedSizeSubscrptionRecoveryPolicy - and the
default cache size for each topic in 5.1 is about 6mb. I'd suggest
conf
13 matches
Mail list logo
