Immediately move a message to the DLQ upon Expiration

Hello, I've searched around but not found an answer to this. We are setting the timetolive header on messages and placing them on a queue. We want this message to be immediately and automatically moved to the DLQ as soon as it has expired, even though the consumer is not connected. What we are

java.io.FileNotFoundException: http://activemq.apache.org/schema/core/activemq-core-5.6.0.xsd

Hey guys, I have been using my broker's configuration successfully for quite a while now, but after updating to Java 7 I am running into the following error: My broker's configuration is as follows: My current configuration is Java *1.7.0_06-b24* with *ActiveMQ 5.6.0* and *Spring 3.1.2*

Stoping MessageListener

I have a MessageConsumer and use the MessageListener. I need to be able to cancel/stop that listener. Any suggestions?? thanks -- View this message in context: http://activemq.2283324.n4.nabble.com/Stoping-MessageListener-tp4662529.html Sent from the ActiveMQ - User mailing list archive at

Re: Does the destination wildcard require at least one character preceding it?

In summary, my test involves a queue where prioritizedMessages=true. I put some messages with varying priorities on the queue, and then GET them off to see if they are retrieved in order of highest priority. My test as a loop doing that many times. When prefetch is zero, it doesn't take many

Re: Stoping MessageListener

None ot those suggestions work. I'm running in NetBeans... here is the code... public class MyFirstActiveMqQueue { private static ActiveMQConnectionFactory connectionFactory; private static Connection connection; private static Session session; private static Destination destination;

Re: Channel was inactive for too long error

I tried to set Inactivity duration like this but activemq didn't start. It says it needs ; at the end. Am I doing something wrong? Caused by: org.xml.sax.SAXParseException: The reference to entity wireFormat.maxInactivityDuration must end with the ';' delimiter. transportConnector

Re: Channel was inactive for too long error

Christian, I do have seen this error a lot, and in fact it's critical. We discussed this with Gary but the bug got closed without a confirmation of a fix ( https://issues.apache.org/jira/browse/AMQ-3353). In fact, I'm writing a test case now because using the Multicast Transport Protocol

Re: Channel was inactive for too long error

If this is closed I am assuming there is a workaround. On Thu, Jan 31, 2013 at 10:52 AM, Andreas Calvo Gómez andreas.ca...@scytl.com wrote: Christian, I do have seen this error a lot, and in fact it's critical. We discussed this with Gary but the bug got closed without a confirmation of a

Increase the temp queue timeout from 30 seconds

Is there a simple way to increase the timeout on the replyto temp queues from 3 ms? (Request/response type implementation using wso2esb and wso2as axis2 services) I have some potentially long running services that are failing because the temp queues are being cleaned up before its done, it

Re: Channel was inactive for too long error

No, it's still an issue really easy to reproduce. I'm trying to get a Use Case well defined, but it's hard to simulate a stalled network using multicast when one can't interfere directly in the connection between the brokers (and the error still relies on handling the TCP connection status).

Re: Channel was inactive for too long error

Sorry, I meant 5.1.2 on the other computer, run ant producer -Dtopic=true -Dmax=99 On 31/01/13 20:17, Andreas Calvo Gómez wrote: 5.1.2 on the other computer, run ant consumer -Dtopic=true -Dmax=99 -- Andreas Calvo Gómez Systems Engineer Scytl Secure Electronic Voting Plaça Gal·la

Re: Channel was inactive for too long error

Thanks! but I am not even able to add maxInactivityDuration to the uri. Is there a workaround for that? On Thu, Jan 31, 2013 at 11:17 AM, Andreas Calvo Gómez andreas.ca...@scytl.com wrote: No, it's still an issue really easy to reproduce. I'm trying to get a Use Case well defined, but it's

Re: Channel was inactive for too long error

try escaping the '' On Thu, Jan 31, 2013 at 11:48 AM, Mohit Anchlia mohitanch...@gmail.comwrote: I tried to set Inactivity duration like this but activemq didn't start. It says it needs ; at the end. Am I doing something wrong? Caused by: org.xml.sax.SAXParseException: The reference to

Re: Channel was inactive for too long error

Thanks! I'll try that. If I apply maxInactivityDuration just on server then would client recognize that? I wanted to disable it to see if it helps. On Thu, Jan 31, 2013 at 12:31 PM, Christian Posta christian.po...@gmail.com wrote: try escaping the '' On Thu, Jan 31, 2013 at 11:48 AM, Mohit

Re: XML Schema location not accessible

On Thu, Jan 31, 2013 at 7:55 PM, Joe Milora jmil...@uci.edu wrote: Hi, We've been using http://activemq.apache.org/schema/core/activemq-core-5.4.1.xsd in our schema file and today it unexpectedly failed, preventing the application from starting. I tried using other schema locations listed on