Hello, I am having a problem successfully shutting down a consumer pool where
there is one outstanding job in the pool. The shutdown sequence will wait
for the job to finish, but the acknowledgement never makes it back to the
queue and thus the queue count is out of whack, here is my code (I am su
Hello, I am having a problem successfully shutting down a consumer pool where
there is one outstanding job in the pool. The shutdown sequence will wait
for the job to finish, but the acknowledgement never makes it back to the
queue and thus the queue count is out of whack, here is my code (I am su
Dejan, thanks for the response.
I removed the line, but I am still seeing the message de-queued immediately.
On the server side, I have set the schedulerSupport="true" in my
conf/acticemq-specjms.xml file, not sure what else to do ...
--
View this message in context:
http://activemq.2283324.n4.
The message is sent and goes through, but it is dequeued immediately, it does
not wait the time specified in the header.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Scheduler-Broken-tp3545460p3545468.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
I have tried both 5.4.2 and 5.5 and have been unable to get the scheduler to
work. I have set
schedulerSupport=true in the activemq-specjms.xml file.
My code looks as follows:
public void scheduleMessage() throws JMSException {
Destination destination = new
ActiveMQQueue("OutboxTwitterU
