Nope :( It still happens from time to time. Restart of the services helped
us, so we do it from time to time.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Broker-log-full-of-Failed-to-register-queue-messages-tp4685241p4696875.html
Sent from the ActiveMQ - User mailing
Hi, I am using a cluster of 2 brokers connected via Duplex connector. Brokers
version is 5.10.0, Windows Server 2012 R2, java = SE 1.7.0_51-b13.
Recently I found that both brokers log is full of the same messages:
Full text of warning:
2014-09-02 07:37:41,430 | WARN | Failed to register queue://
Thanks for the help! I would re-read these articles. But could you draft the
worthwhile configuration for me? Is it enough to just increase http://activemq.2283324.n4.nabble.com/OutOfMemoryError-due-to-TopicSubscription-tp4664025p4664128.html
Sent from the ActiveMQ - User mailing list archive at Na
I am not sure why it uses a bridge to destination feature. Is there another
way to configure it? (sysadmin did it that way, not me)
But I wonder is 6 bridges is really a high number? How many resources does
it take to support a separate advisory topic subs? Here is the full config:
http://www.spr
I don't use advisory topics, but I do use network of brokers. There are 2
brokers and they are connected by network connector per queue basis. Here is
the example:
:62626)"
networkTTL="2"
prefetchSize="1"
duplex="true">
Hi,
Recently our live AMQ 5.7.0 server on Windows experienced OutOfMemory
exception. I've read the article
http://blog.garytully.com/2009/07/apache-activemq-out-of-memory.html that
states that it is usually a problem of configuration. I also read FAQ page
http://activemq.apache.org/javalangoutofm
I managed to resolve the issue by restarting 2nd broker. But I want to
understand why it is happened.
> Is your client using failover?
Yes, it does. Moreover I am using 2 duplex connectors from one broker to
another with conduitSubscriptions = "false" on both connectors.
If so was there a broker
There were a situation in my production environment when an application
couldn't create a consumer. It looks like a thread freeze for infinite.
There are no exceptions or errors happen, but the thread got blocked.
I am using AMQ 5.6.0 with the latest NMS client library.
I created a dump file an
Recently, I have changed the configuration of the broker network and set a
duplex connection between 2 of my brokers. So, the first broker creates 3
duplex conections to another one.
I also set conduitSubscriptions=false on both connectors. I have about 200
consumers that are connected to a queue
Created a ticket in Jira - https://issues.apache.org/jira/browse/AMQ-3758
I would love to fix this problem, but I am no a Java developer. :(
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Scheduler-exception-java-io-IOException-Could-not-locate-data-file-tp4437905p4449987
Is it possible to recover database? I found that there are special
configuration that could help restore main ActiveMQ database.
But I can't see if that is working for scheduler database. Can anyone
confirm that? Or is there a special configuration parameter for restoring
schedul
Hi, I use ActiveMQ 5.5.0 and I use AciveMQ scheduler to organize delayed
delivery. I found exceptions like that in my broker logs:
2012-03-02 03:26:08,234 | ERROR | JMS Failed to schedule job |
org.apache.activemq.broker.scheduler.JobSchedulerImpl | JobScheduler:JMS
java.io.IOException: Could not
Ok, it seems I figured out the answer. It is states for NMS provider, but I
think it is more general problem.
The problem reproduces if you have a consumer with 0 prefetchSize. In this
case a call to MessageConsumer.SendPullRequest gives true on the following
condition:
if (this.info.PrefetchSize
I am using ActiveMQ web console to monitor ActiveMQ performance. And I've
found a very strange statistics in my brokers.
I use failover in AMQ 5.5.0 and there is a queue which has 100 consumers.
Roughly, I run through the queue about 300k messages a day. I use individual
acknowledge mode and if th
It is hard to reproduce this problem in a test case.
But I do use latest version of ActiveMQ.NMS. I am also think about upgrading
5.5.0 ActiveMQ to 5.6.0 to resolve the problem with Scheduler (I use it for
redelivery).
Can you recommend me anything to get closer to the root of the problem?
--
Vie
I am using 2 ActiveMQ brokers 5.5.0 with failover on Windows. I have a C#
windows service which connects to the broker queue via NMS. Windows service
creates 100 threads and each thread has its own consumer. I use
AutoAcknowledge mode. I run 4 instances of the windows service on separate
machines.
Thanks! Yeah, I thought about that. Okay I will set expiration time.
Well, redelivery policy is working not as good as I supposed it to work.
First of all, it blocks consumer to receive other messages until redelivery
policy time reached. If you apply patch that makes consumer non-blocking
then y
I have a queue where I store messages without expiration time. A consumer
process messages, but it is okay that it can't successfully process them
from the first try. If processing failed I resend message to the same queue
with a delayed delivery (using scheduler). If a message can't be processed
a
I've encountered a problem of hanging up of the producers and I found that it
is related to "Producer Flow Control". I made a quick fix via disabling
producerFlowControl at all. But now I wonder what should I do, because I
don't really want producers to use all available disk space.
The questions
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
It seems I found the problem. It was a well-known problem of .NET: Connect()
method of the socket class doesn't have timeout property.
http://www.codeproject.com/KB/IP/TimeOutSocket.aspx And it takes from 20 to
30 seconds for .NET to understand that connection cannot be established.
I've implement
Yes, I am using NMS client.
If I remove every parameter as you adviced and try to send a message when
broker-2 is turned off I get "connect fail" message in log after ~20 seconds
passed. So, I believe that my parameters have no effects on this at all. Can
I miss something?
--
View this message i
ActiveMQ version is 5.5.0.
Yes, the port is not listeneed at all, because I stop ActiveMQ windows
service for broker-2.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Connection-timeout-20-sec-tp4076349p4076625.html
Sent from the ActiveMQ - User mailing list archive at Nab
I have 2 failover brokers and the following configuration:
failover:(tcp://broker-1:61616,tcp://broker-2:61616)?randomize=true&transport.initialReconnectDelay=10&transport.startupMaxReconnectAttempts=1&transport.maxReconnectDelay=1000&transport.useExponentialBackOff=false&transport.timeout=3000&tr
Okay, it seems I have 2 options:
1) Merge all changes from Java into NMS
2) Try to use camel case routes to define a rule. The scheme will be the
following:
* Consumer receives a message and it can't process it
* Consumer move message to its own DLQ, which is actually works as a
temporary storage
Great! Adding transport. prefix fixed the problem. Thanks!
--
View this message in context:
http://activemq.2283324.n4.nabble.com/failover-startupMaxReconnectAttempts-doesn-t-do-anything-tp3735372p3986136.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Hi, Gary.
Thanks for the answer. I forgot to mention that I am using NMS. Does it make
the difference? I mean, that you gave the link to ActiveMQ client code,
right? Is there something like that for NMS?
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Redelivery-sticks-to-
I experience the same problem using NMS with ActiveMQ 5.5.0
I've tried syntaxis:
failover:(tcp://localhost:61616)?startupMaxReconnectAttempts=1&initialReconnectDelay=1
AND
failover://(tcp://localhost:61616)?startupMaxReconnectAttempts=1&initialReconnectDelay=1
And it doesn't make any difference
Diego, were you able to fix that problem?
I have the same situation and don't know how to make consumer to consume all
"good" messages and leave bad ones until they can be processed again.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Redeliveries-DLQ-AsycError-tp236570
Is there any progress conserning this issue? I am using the latest version of
ActiveMQ 5.5.0 and the situation is the same: consumer threads doesn't
receive any messages until full redelivery cycle is completed.
Can this be somehow resolved? Expected behaviour is: failed to process
message is sent
Hi. I am developing a mail server which is responsible for sending emails.
Prepared emails are delivered to my server via ActiveMQ. I would like to
organize the code in the best way, so it would meet the following
requirements:
* Every email that is read from the queue should be delivered to the
r
Hello everyone.
I use Apache.NMS and its two main interfaces: IMessageProducer and
IMessageConsumer. I have created a wrapper on a IMessageProducer and
IMessageConsumer, so my system wouldn't know that ActiveMQ is used
underneath.
I can implement wrappers using following scenario:
1. I can creat
I experience the same problem with redelivery with Individual acknowledgement
mode. I've looked at the example, but every test case uses
Session.AUTO_ACKNOWLEDGE. It raises 2 questions:
1. So, why should Individual acknowledgement mode be used?
2. I don't see where transaction is started... Does i
Hi, I am using ActiveMQ 5.5.0 with NMS.
I want to make a reliable system and confirm that every message is
processed. I want to check that if I don't acknowledge the message it will
be redelivered again. I want to explicitely acknowldge every message so I
have picked Individual acknowledge mode. I
34 matches
Mail list logo
