Hello.
I've a question:
We're using the failover protocol, with NMS 1.5.1 and ActiveMQ 5.5.
When we stop the ActiveMQ, and start it again, sending messages
still works for the clients, but no new messages are received.
We use asynchronous listening (subscribe to Listener).
Do we need to do
I downloaded activemq 5.5.1 and can guarantee 2 out of 100 messages sent to it
are lost when using transacted routes (route A to route B below). Is this the
right place to ask for help? This is my actiemq/camel config.
beans
xmlns=http://www.springframework.org/schema/beans;
I've managed to sort it after reading around. Not really sure what the problem
was but it's fine now :)
Alistair
--
mov eax,1
mov ebx,0
int 80h
On 21 Nov 2011, at 09:06, Alistair Young wrote:
I downloaded activemq 5.5.1 and can guarantee 2 out of 100 messages sent to
it are lost when
There's an open issue for it https://issues.apache.org/jira/browse/AMQ-2469
Any contributions are welcomed :)
Regards
--
Dejan Bosanac - http://twitter.com/dejanb
-
The experts in open source integration and messaging - http://fusesource.com
ActiveMQ in Action -
Hm, it seems that I don't fully understand how consumers are working.
I've merged fix from the JMS and it seems working nice if there is a small
amount of messages to resend. But if I try to put a big amount of bad
messages in queue, I will still get the same behavior: all my consumers got
stuck.
Hey,
Small question here : suppose I have two Consumers (DMLC in Spring - started
in two different application contexts - two Java VMs), both listen to the
same Queue.
Now I want to keep the DMLC Container started, but at the same time I want
to be able to disable one of them. And when I say
I think you're referring to the prefetch limits:
http://activemq.apache.org/what-is-the-prefetch-limit-for.html
Many messages (by default) will be sent to a consumer before an
acknowledgement is received by the broker.
Consumer can pull messages (if you really want that) by setting prefetch to
0.
I might be wrong, but just trying.
How about if you start your own broker instance through
BrokerService broker = new BrokerService();
broker.setBrokerName(fast);
broker.getSystemUsage().getMemoryUsage().setLimit(64*1024*1024);
PolicyEntry policy = new PolicyEntry();
policy.setMemoryLimit(4 *
Resending after subscribing to mail list... I think...
--
It looks like an attempt was made to fix AMQ-2489 with CMS revision 883469.
https://issues.apache.org/jira/browse/AMQ-2489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel#issue-tabs
The broker will dispatch messages to consumers in batches before client's ack,
then the client will dispatch each message to consumer who is interesting in.
Messages that process unsuccessfully, says messageListener throws
RuntimeException, will be redispatched to messageLisener by client if not
Thanks mickhayes,It's my careless to miss some important code when client
acknowledges, the broker will wakeup destination to dispatch more messages to
consumers again, it's what I expect.
At 2011-11-21 22:31:12,mickhayes mickha...@gmail.com wrote:
I think you're referring to the prefetch
So what your are trying to say is what I have mentioned: run-time this is not
possible. You have to manually shut down the DMLC, which kind-of sucks :(
--
View this message in context:
http://activemq.2283324.n4.nabble.com/ActiveMQ-Dispatcher-Policy-tp4091599p4092470.html
Sent from the ActiveMQ
Could Timothy Bish or someone else provide details on issue AMQCPP-376? We
are running in to this issue on our production system. Is there a good way
to work around this while keeping the Failover transport?
The underlying deadlock issue is still there in trunk, so even though you
didn't see it
On Mon, 2011-11-21 at 11:30 -0800, greenbean1 wrote:
Could Timothy Bish or someone else provide details on issue AMQCPP-376? We
are running in to this issue on our production system. Is there a good way
to work around this while keeping the Failover transport?
There's been no time for me
On Mon, 2011-11-21 at 07:31 -0800, greenbean1 wrote:
Resending after subscribing to mail list... I think...
--
It looks like an attempt was made to fix AMQ-2489 with CMS revision 883469.
As you said, you could stop the DMLC which implements interface Lifecycle or
restart it via jmx command.
At 2011-11-22 02:03:35,Eugene eugen.ra...@gmail.com wrote:
So what your are trying to say is what I have mentioned: run-time this is not
possible. You have to manually shut down the DMLC,
Hi,
I downloaded activemq-web-demo-5.5.1.war from
http://repo1.maven.org/maven2/org/apache/activemq/activemq-web-demo/5.5.1/
http://repo1.maven.org/maven2/org/apache/activemq/activemq-web-demo/5.5.1/
and put into Tomcat webapps directory, but has below error:
Does anyone deploy it without
Hi,
SLF4J said 1.5.11 is not compatible with Java 6, so I remove 1.5.11 with
slf4j-api-1.6.4.jar, logback-classic-1.0.0.jar, and logback-core-1.0.0.jar.
Tomcat also told me that servlet-api-2.5.jar won't be loaded.
Now I am facing below:
--
View this message in context:
Hi,
For java.lang.IllegalStateException: !(Jetty || Servlet 3.0 ||
ContinuationFilter),
I did below change in web.xml of web demo:
Strange!
--
View this message in context:
Hi,
I check source code of org.apache.activemq.web.SessionFilter and found
this filter is needed.
So I modified web.xml of web demo application as below:
OK~Now AJAX stock portfolio demo works with Tomcat 6.
Then I copied same web demo application to webapps directory of Tomcat7, but
got below
20 matches
Mail list logo
