any help on this would be greatly appreciated... =)
srasul wrote:
>
> Hi,
>
> when dealing with slow/deadlocked consumers, it seems that one thing that
> really helps is setting the MaximumPendingQueueSize in the subscription
> via JMX Console.
>
> My questions are
Hi,
i am starting a broker via spring config and i would like to enable the
LoggingBrokerPlugin it in. I am doing this via:
ClassPathXmlApplicationContext app = new
ClassPathXmlApplicationContext("activemq-spring.xml");
XBeanBrokerService broker =
(XBeanBrokerService)app.getBean("broker
Hi Phill,
from what i can see, you are sending persistant messages to a topic, this
means that if no one is listening on that topic, your messages will he
stored (aka held in memory) until someone listens on that topic. this would
explain why you run out of memory. Essentially you experiencing th
Hi,
sometimes our activeMQ freezes with the JMX console reporting that the
Borker's MemoryPercentUsed is 100%.
In out activeMQ setup, we have no queues and _only_ topics. We have this to
avoid the memory issues related with slow-consumers.
we are running activeMQ 4.1.1.
What is also strange is
any info about this?
srasul wrote:
>
> Hi,
>
> We have been having cases recently were people cannnot connect to our
> ActiveMQ (4.1) when using proxies. After lots of digging, i have found
> that the issue may be in this class:
> org.apache.activemq.transport.tcp.TcpTra
, at 4:20 PM, srasul wrote:
>
>>
>> Hi there,
>>
>> i was doing some testing with compression, and i have found that both
>> producer and consumer need to have compression enabled in the
>> connection url
>> for compression to work. is this normal behavi
Hi there,
i was doing some testing with compression, and i have found that both
producer and consumer need to have compression enabled in the connection url
for compression to work. is this normal behavior?
I did some testing by doing a network trace and found:
- for compression to work, i have
Hi,
We have been having cases recently were people cannnot connect to our
ActiveMQ (4.1) when using proxies. After lots of digging, i have found that
the issue may be in this class:
org.apache.activemq.transport.tcp.TcpTransport and especially in the
connect() method. There we call remoteAddress.
Hi,
ActiveMQ makes it very easy to create JMS Destinations, but seems like they
are not every easy to destroy.
does this mean that i will case ActiveMQ to crash if i create too many JMS
Destinations?
Also if a destination is created, and unused, is it cleaned up or destroyed?
Regards,
Saqib
-
the MBean for the topic after about an hour I see:
> DequeueCount: 472089
> DispatchCount: 472225
> EnqueueCount: 24139
>
> Does this sound normal? And do you know whether there's any documentation
> relating to the attributes exposed by the MBeans?
>
>
>
> srasul
Hi,
I am no activeMQ expert... but... this might be the "fast-producer &
slow-consumer" issue. If you use Queues, and there is fast producer and a
slow consumer, you will eventually run out of memory.
this is because JMS has guaranteed message delivery. meaning any message you
send must be deliv
11 matches
Mail list logo