Thanks,
Pawan
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Producer-keeps-allocating-memory-tp4667880p4667992.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
On 06/06/2013 06:09 AM, Jean Silga wrote:
Can anyone help me with this?
Doubt anyone can help until you provide some more specific on which
LRUCache instance you are referring to since its used in several places
throughout the client and broker code.
On Wed, Jun 5, 2013 at 6:24 PM, Jean Sil
Take a look at this method:
http://docs.oracle.com/javaee/6/api/javax/jms/MessageProducer.html#send(javax.jms.Destination,%20javax.jms.Message,%20int,%20int,%20long)
On Thu, Jun 6, 2013 at 4:30 AM, ssahu wrote:
> > This is regarding active mq topic.
> > Recently we have seen issue of head dump
On 06/05/2013 05:15 PM, Chris wrote:
Hi,
I have a situation in which i need to close a client cms::connection block
inside a cms::connection::start(), from a different thread. In this case, no
broker as been started yet and i'm using failover. so the thread is blocked
inside connection.start() (
Hi,
I have a situation in which i need to close a client cms::connection block
inside a cms::connection::start(), from a different thread. In this case, no
broker as been started yet and i'm using failover. so the thread is blocked
inside connection.start() (which is expected). However to close an
> This is regarding active mq topic.
> Recently we have seen issue of head dump saying Topic containing huge
> number of messages which is taking lot of memory. It seems topic messages
> were not consumed by the consumer, might be(not sure) because the
> consumer died due to some other reason.
>
Inline
On Thu, Jun 6, 2013 at 8:08 AM, Jesus Roncero wrote:
> On Wed, Jun 05, 2013 at 08:57:01AM -0700, Christian Posta wrote:
>
> Hi,
>
> further on this:
>
> > Sounds like it's happening exactly as you have it configured.. I assume
> > you're using non-persistent messages?
> >
> > As Joha
On Thu, Jun 6, 2013 at 8:09 AM, Jesus Roncero wrote:
> On Thu, Jun 06, 2013 at 07:45:30AM -0700, Christian Posta wrote:
> > Oh I see... because you have producer flow control turned off. The memory
> > limits won't be taken into account, even when their full. You would have
> to
> > plan around t
On Thu, Jun 06, 2013 at 07:45:30AM -0700, Christian Posta wrote:
> Oh I see... because you have producer flow control turned off. The memory
> limits won't be taken into account, even when their full. You would have to
> plan around that in subsequent configuration details, in this case you're
> us
On Wed, Jun 05, 2013 at 08:57:01AM -0700, Christian Posta wrote:
Hi,
further on this:
> Sounds like it's happening exactly as you have it configured.. I assume
> you're using non-persistent messages?
>
> As Johan pointed out, your config kinda doesn't make sense :)
>
> The is an overall broke
We are running in to an issue where connection attempts made via the
FailoverTransport in CMS 3.6 seem to leak socket descriptors. Does anyone
have any suggestions as to where we can look to figure out what is
happening?
The problem is easy to reproduce by connecting a process using CMS to an
Act
Oh I see... because you have producer flow control turned off. The memory
limits won't be taken into account, even when their full. You would have to
plan around that in subsequent configuration details, in this case you're
using file pending message cursor for the queue subscriptions which, when
h
On Wed, Jun 05, 2013 at 09:03:15AM -0700, Christian Posta wrote:
> was just thinking... for question #3, it would make sense if the overall
> broker memory was 500MB and your temp was 100MB... then when you hit the
> cursor high water mark at some point (70%) it would spook to disk and
> overload t
Hey
I feel so ashamed, but after a short pause and caring about something else I
found the issue (at least I hope I did ^^).
As mentioned I followed several documentations, and one of them had
rebalanceClusterClients="true" as part of the parameters for the transport,
besides updateClusterClients
Hi everyone
I am "playing around" with AMQ and want to set up a small cluster of
brokers. I have two VMs flying around, Ubuntu based, installed AMQ 5.8,
everything fine so far.
I followed basically
http://activemq.apache.org/networks-of-brokers.html#NetworksofBrokers-Purestaticnetworks
and some ot
Can anyone help me with this?
On Wed, Jun 5, 2013 at 6:24 PM, Jean Silga wrote:
> I tried in two places without success.:
>
> 1) In the destination policy of the broker
>
> amq.'broker'(id: 'broker', brokerName: 'localhost', useJmx: true,
> persistent: false, advisorySupport='tru
16 matches
Mail list logo
