I have observed that when sending delayed delivery messages (with
AMQ_SCHEDULED_DELAY values in the header), ActiveMQ does not seem to be
including the delivery in the original transaction. This results in
duplicate messages being delivered in my setup. Here is how I tested:
1. Send a message to a
Cuz its broke...
Sent from my Verizon Wireless 4G LTE Smartphonechudak
wrote:I have an existing RedeliveryPolicy configured thusly:
This has been working fine up through 5.5.1. Today I upgraded to 5.7.0 and
now my application won't start:
y'; nested exception is
org.
I have an existing RedeliveryPolicy configured thusly:
This has been working fine up through 5.5.1. Today I upgraded to 5.7.0 and
now my application won't start:
y'; nested exception is
org.springframework.beans.factory.BeanCreationException: Error creating bean
with nam
Hi,
I am using activemq 5.7 with spring 2.5 on the consumer side. I configured
the redelivery policy on the broker side. when doing the load test, i found
the below two problems.
1.Exception is thrown as below.
org.springframework.jms.IllegalStateException: The Session is closed; nested
exceptio
Interesting I think I'm seeing the same with the web console on 5.7.0.
I have a queue that's constantly got a "Number of Pending Messages" count
of 4. Yet the consumer is processing messages quite happily and is often
waiting for new messages. The Dequeued count is occassionally rising.
I am tryi
When looking at the Queue size attribute in JConsole for a particular
Queue we noticed that the size would not reseed below a certain number
138. The reporting of this number persisted for several hours. When I
investigated it I looked at the Queue's operation browseMessages it
returned what I
I am using 5.7.0 with Java 1.7.0_07 on a linux 64 system. Messages are
persisted using KahaDB as the store.
* I have a test which puts 10 messages on a queue. This queue is being read
via a transacted consumer.
* I then shutdown the broker without committing or rolling back the session.
I am d
> AFAIR there is a reloadLog4jProperties() JMX operation in the Broker MBean.
> Could you test and confirm?
Yes, that one works as expected. I have tested it various times.
Torsten Mielke
tors...@fusesource.com
tmie...@blogspot.com
On Oct 26, 2012, at 12:42 PM, Raul Kripalani wrote:
> AFAIR
AFAIR there is a reloadLog4jProperties() JMX operation in the Broker MBean.
Could you test and confirm?
Regards,
*Raúl Kripalani*
Apache Camel Committer
Enterprise Architect, Program Manager, Open Source Integration specialist
http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripala
Thx
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Start-5-durable-subscribers-simultaneously-broker-throw-OutOfMemory-exception-tp4658276p4658284.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
On Oct 26, 2012, at 7:25 AM, Liu fuming wrote:
> There is 1GB durable topic messages left in KahaDB files ,with 1 mb size per
> message.Then start 5 durable subscribers simultaneously to receive the
> stored messages,the Broker run out of memory immediately. There's one way to
> prevent this from
There are a couple of unit tests that setup the same.
Perhaps have a look in activemq-core/src/test/java/org/apache/activemq/network
package for example code.
Regards,
Torsten Mielke
tors...@fusesource.com
tmie...@blogspot.com
On Oct 22, 2012, at 11:03 PM, newUser06 wrote:
> Hi,
> I am new
12 matches
Mail list logo
