10 Feb 11:07
9 Feb 16:20
Re: Master/Slave failover: Consumer get less messages it should.
Hi, I’ve the following situation when failover is produced artificially by killing the master (I´m talking about a master/slave configuration): Inmediatly after the consumer connects the slave, it begins to receive any messages that previously where delivered by the master due to the fact that the destination it subscribes was defined as retroactive. The problem is the consumer doesn’t get all the messages it should receive. It just receives a portion of it, from where it begins to produce the following warning: 12-02-07 13:37:51:756 [ActiveMQ Session Task] DEBUG org.apache.activemq.ActiveMQMessageConsumer - (ActiveMQMessageConsumer.java:1226) ID:radeon-5594-1328632514518-0:0:1:1 ignoring (auto acking) duplicate:… I suspect perhaps this is related with: https://issues.apache.org/jira/browse/AMQ-2751 But I´m running ActiveMQ 5.3.2 and I can’t update to 5.4.3. Could you help me to work around this issue? -- View this message in context: http://activemq.2283324.n4.nabble.com/Master-Slave-failover-Consumer-get-less-messages-it-should-tp4366155p4373187.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
9 Feb 14:46
Re: Master/Slave failover: Consumer get less messages it should.
Hi, this reply is just to ensure the original question is dispatched to the mailing list. Regards, Guillermo. -- View this message in context: http://activemq.2283324.n4.nabble.com/Master-Slave-failover-Consumer-get-less-messages-it-should-tp4366155p4372871.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
8 Feb 00:40
strange topic subscriptions not disappearing [V5.5.1]
Hi there,
we are still testing AciveMQ in preproduction here. Imagine following
situation:
we have two topics here that work as a request/response pair. The data
producer is permanently(not durable) subscribed to the request topic and
puts its payload into the response topic. The client uses a JMS Template
with a SessionCallback to sends its data requests to the request topic and
awaits responses in the response topic. Here the code that matters:
@Override
public Message doInJms(final Session session) throws JMSException {
MessageConsumer consumer = null;
MessageProducer producer = null;
try {
final String correlationId = UUID.randomUUID().toString();
consumer = session.createConsumer(responseDestination,
"JMSCorrelationID = '" + correlationId + "'");
final ObjectMessage message =
session.createObjectMessage(payload);
message.setJMSCorrelationID(correlationId);
message.setStringProperty("CLIENT_ID", clientUid);
message.setStringProperty("GSE_ID", gseUid);
producer = session.createProducer(requestDestination);
producer.send(message);
return consumer.receive(TIMEOUT);
(Continue reading)
7 Feb 14:17
ActiveMQ.NMS consumer hangs after sometime
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. PrefetchSize is set to 1 and I use synchronous receive method with small (10 ms) wait time. I also have the following setup on brokers for queues: <policyEntry queue=">" producerFlowControl="false" memoryLimit="1mb"> After working for some period of time (usually a day or two) all consumers stop receiving any messages, but I can see messages in brokers. Usually all windows service instances stop receiving messages simultaneously, but not every time. If I restart services then they start processing messages. I've created a dump file and I found a lot of threads are waiting for a mutex to be released. Here is the stack trace: System.Threading.Monitor.Wait(System.Object, System.TimeSpan) Apache.NMS.ActiveMQ.Util.SimplePriorityMessageDispatchChannel.Dequeue(System.TimeSpan) Apache.NMS.ActiveMQ.MessageConsumer.Dequeue(System.TimeSpan) Apache.NMS.ActiveMQ.MessageConsumer.Receive(System.TimeSpan) I also have a lot of DedicatedTaskRunners waiting for something: System.Threading.Monitor.Wait(System.Object) Apache.NMS.ActiveMQ.Threads.DedicatedTaskRunner.Run() System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)(Continue reading)
7 Feb 10:20
Apollo 1.0 AssertionError on queue browser creation
Hello,
When the Stomp client opens a queue browser, the broker logs an
AssertionError:
send:
CONNECT
login:admin
passcode:password
accept-version:1.0,1.1
server:localhost
heart-beat:0,0
received:
CONNECTED
version:1.1
server:apache-apollo/1.0
session:mybroker-1238
heart-beat:100,10000
user-id:admin
send:
SUBSCRIBE
destination:/queue/TOOL.DEFAULT
id:{28C1F8E4-3125-4FDD-B2A6-CC14DCDE9EE3}
send:
SEND
destination:/queue/TOOL.DEFAULT
(Continue reading)
7 Feb 09:05
Apollo 1.0 unsubscribe durable subscriptions not successful
Hello, with the final release, using Stomp 1.0 and 1.0, the broker still sends messages to the client after unsubscribing. Is this designed as different from ActiveMQ? The sequence is: * connect, create durable subscription "test", disconnect * connect, send message to durable subscription "test", disconnect * connect, destroy durable subscription "test", disconnect * connect, create durable subscription "test", disconnect * connect, read a message -> this fails in ActiveMQ but the message still is present in Apollo send: CONNECT login:admin passcode:password accept-version:1.0,1.1 server:localhost heart-beat:0,0 client-id:test received: CONNECTED version:1.1 server:apache-apollo/1.0 session:mybroker-d0f heart-beat:100,10000(Continue reading)
7 Feb 04:40
Question about activemq queue message events
Hello, I'm actually asking this question on behalf of one of our developers. As I understand ActiveMQ (and Servicemix), when a message is placed into a queue, an event is fired off telling the consumer a new message is now present. It is then the consumer's job to pick up the new message and process it. We had a recent issue where it appeared that new message arrival events were either not firing or firing off very slowly to the consumer as messages were placed into the queue. So, the message queue was backing up and messages were not being processed. Note that we have about 8 different queues on this Servicemix server, but only one of the queues exhibited this behavior. As a result, the processing ground to a halt on this specific queue and queue messages backed up. Once we restarted everything involving servicemix, activemx and the consumer of the queue, everything went back to normal processing speed. I'm trying to determine if there are any known issues that could cause this behavior within ActiveMQ. We are running Apache Servicemix version 4.3.1-fuse-01-09 using ActiveMQ version 5.4.2 (looks like the ActiveMQ packages were included with the Servicemix package). As another question, since it appears ActiveMQ was included in the Servicemix package, should I ask this question on the Servicemix forum instead? Any help would be appreciated. Thanks.(Continue reading)
6 Feb 23:37
Remove SNAPSHOT from build version
I want to create an internal build of ActiveMQ and I've been trying to remove SNAPSHOT from all the versions and JAR file names. I've tried versions:use-releases and versions:set, but it only seems to partially work. When I look into the zip file or tarball that gets created, a lot of the JAR files still have SNAPSHOT in the name. What is the process to create a "release"? Chris
6 Feb 14:26
configuration sample to connect 2 machines
Hi - I am new to ActiveMQ and have it installed and I have run OK the "and/consumer" and also "ant/producer" samples. But this environement (all in one machine) is very restricted. The real world is when you want to go to another machine. *Can someone provide a pointer to a ActiveMQ configuration to send messages from one machine and to receive them on another machine ? * I dont want to use JNDI, as I prefer to "code" the destination in my app (or its cfg files). Thanks. Ramon. -- View this message in context: http://activemq.2283324.n4.nabble.com/configuration-sample-to-connect-2-machines-tp4361227p4361227.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
6 Feb 10:30
Re: activemq crashed
I have experienced exactly the same exception just recently despite I have been using v. 5.4.2 for a year and have never before seen this... I found something like it on jira 3131(https://issues.apache.org/jira/browse/AMQ-3131), but cannot just upgrade to the next version and cannot consistently recreate the scenario. Any ideas how to recreated the problem? Best regards Trym -- View this message in context: http://activemq.2283324.n4.nabble.com/activemq-crashed-tp4253080p4360760.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
RSS Feed