Ajit,
I agree with Clebert's statement that the message, once delivered to the
consumer, should not be within the broker's control to expire. Once it's
been delivered, it's outside of the broker's control and is the client's
responsibility to deal with appropriately.
However, I agree with your as
This looks like the same behavior captured in
https://issues.apache.org/jira/browse/AMQ-5730, which unfortunately has
been open and unworked since April 2015. I've added a comment to that story
noting that you hit the same problem and adding what I found based on my
searching in the source code.
T
Mike,
Can you give me more to work with? Maybe a full stack trace rather than
just a reference to an unqualified classname? I'm willing to try to help,
but I'm not familiar with the JAAS/LDAP code and your description didn't
give me a clear understanding of which code you were in when you saw the
Hello,
Is there a way to dynamically add a plug to an already started broker? I
tried the following to no avail.
BrokerService brokerService = BrokerRegistry.getInstance().findFirst();
ActiveMQBrokerPlugin bp = new ActiveMQBrokerPlugin();
brokerService.setPlugins(new BrokerPlugin[]{bp});
I moved the directory to c:\ActiveMQ I still get the same error so it's not
the nested level of the directory.
Not sure where to go from here it's having issues with the URL protocol on a
windows system path "c:\"
It keeps parsing out the "c:" instead of inserting the "file" protocol.
Mike
--
MessageTransformer plugin has access to a message. I wonder what would be a
proper way to handle exceptions occurred while performing transformations
and how actual message can be accessed in the exception handler?
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
We implemented a queue which should retry the messages on it when there is an
exception.
This is done through ActiveMQ(5.11.1) and Spring. The requirement is to have
the message processing parallel with the messages not being dependent on
each others retry schedule.
Issue : When there are multipl
We implemented a queue which should retry the messages on it when there is an
exception.
This is done through ActiveMQ(5.11.1) and Spring. The requirement is to have
the message processing parallel with the messages not being dependent on
each others retry schedule.
Issue : When there are multipl
clebertsuconic wrote
> As long as the consumer is holding the queue, the message should not
> be expired.
But then why when we browse the queue from ActiveMQ admin console the
message expired even though it was not acknowledged by the client?
--
Sent from: http://activemq.2283324.n4.nabble.co
