Looks like you've heat a flow contorl problem - try disabling it - see
http://activemq.apache.org/producer-flow-control.html
cheers,
Rob
On 14 May 2009, at 11:33, KumarR wrote:
Hi All ,
I am having problem with publishing messages to Topic. It's taking
too much
time to publish a messag
HI there,
are you looking at JConsole to determine this ? --- I think you are
running into
a particular behavior with ActiveMQ. The Time To Live is not regularly
checked
(there is no cleanup thread for ttled messages). To be more concrete
the TTL is checked
checked when the message is dispa
I sended to queue a message after message setting TTL(time to live : 30
second)
then i waited for 2 minute ,
but the message didn't expire.
why ?
--
View this message in context:
http://www.nabble.com/a-question-about-TTL%28time-to-live%29-...--tp23551953p23551953.html
Sent from the Act
Tim, please ignore this message. As I suspected, it was a bad message.
BTW, I am using 2.2.5
thanks
Nishant
Timothy Bish wrote:
>
> On Thu, 2009-05-14 at 12:23 -0700, nmittal wrote:
>> I am writing a high volume tick handler (25000 msgs/sec). Everything
>> works
>> fine for some time and then
On Thu, 2009-05-14 at 12:23 -0700, nmittal wrote:
> I am writing a high volume tick handler (25000 msgs/sec). Everything works
> fine for some time and then I get...
>
> unable to allocate memory for mutex; resize mutex region
> caught unknown exception
> FILE: activemq/core/ActiveMQConsum
I am writing a high volume tick handler (25000 msgs/sec). Everything works
fine for some time and then I get...
unable to allocate memory for mutex; resize mutex region
caught unknown exception
FILE: activemq/core/ActiveMQConsumer.cpp, LINE: 505
FILE: activemq/core/ActiveMQSession
I executed ActiveMQ on windows, everything is ok, I used both JMS client and
Message Bean. both worked.
But when I ran ActiveMQ linux version on Linux(Redhat), Message Bean worked
, however my JMS client only can send Message to Queue, can not receive
message, does anybody know the reason?
--
Vi
In what cases do you envisage a send to one queue failing and a send
to an ExceptionQueue succeeding?
Would this be use in conjunction with some per queue limits?
I guess the question is, what is the supporting use case? There may be
some other way to achieve what you want with ActiveMQ.
2009/5/1
On Thu, May 14, 2009 at 10:18 AM, lbolanos wrote:
>
> Hi
>
> I am wondering if ActiveMQ have plans to support something like
> JMS_OracleExcpQ.
>
> JMS_OracleExcpQ - queue name to send the message to if it cannot be
> delivered to the original destination.
This is why the dead letter strategies e
Hi
I am wondering if ActiveMQ have plans to support something like
JMS_OracleExcpQ.
JMS_OracleExcpQ - queue name to send the message to if it cannot be
delivered to the original destination.
Thanks in advance
Leo
--
View this message in context:
http://www.nabble.com/Feature-like-JMS_Oracle
I have similar problem. However:
I can start with bin/activemq and it works perfectly.
When I use bin/linux-x86-32/activemq i get mentined UnknownHostException
where the host is: ..
the stacktrace:
jvm 1| ACTIVEMQ_HOME: ../..
jvm 1| ACTIVEMQ_BASE: ../..
jvm 1| Loading message broker
Hi,
Thanks for the reply .
When observed in Broker Statistics in Jconsole it has enough memory.
Here is my ActiveMQ.xml file ..
http://www.nabble.com/file/p23539624/activemq.xml activemq.xml
Here is the Memory Snapshot of ActiveMQ Old Generation.
http://www.nabble.com/file/p23539624/Ol
can you give more memory resources to the broker? I imagine there is
some spooling to disk under high load. It may make sense to post your
activemq.xml.
2009/5/14 KumarR :
>
> Hi All ,
>
> I am having problem with publishing messages to Topic. It's taking too much
> time to publish a message. Belo
Hi All ,
I am having problem with publishing messages to Topic. It's taking too much
time to publish a message. Below are the details.
Test Case:
The Client is publishing messages to RequestQueue. and waiting responses on
ResponseTopic using a co-relation id.
Server program consuming messages
Hi,
you should make sure that management context creates a connector. Remove the
following from your configuration if present
Cheers
--
Dejan Bosanac
Open Source Integration - http://fusesource.com/
ActiveMQ in Action - http://www.manning.com/snyder/
Blog - http://www.nighttale.net
15 matches
Mail list logo