bumping the post. Any chance 5.3.1 be released on the beginning of February?
Cheers,
Daroo
--
View this message in context:
http://old.nabble.com/Timeframe-for-5.3.1-release-tp26728777p27330182.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Hi,
any news regarding the release date?
Cheers
Daroo
--
View this message in context:
http://old.nabble.com/Timeframe-for-5.3.1-release-tp26728777p26890017.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Hi,
I was also getting the same exception while using KahaDB as persistance
adapter and producer flow control off, but it seems to be fixed in the
latest 5.4.0 snapshot. I'm not sure, but maybe that was the issue:
https://issues.apache.org/activemq/browse/AMQ-2481
--
View this message in conte
Ok, I've just created JIRA case for this and attached an unit test which
bases on the sample client code from my first post here.
Link to JIRA: https://issues.apache.org/activemq/browse/AMQ-2489
Hope this helps.
Gary Tully wrote:
>
> it looks like a bug. Best approach is to open a jira issue
Thanx for the response but it still doesn’t clarify why I am getting this
strange exception. I understand the difference between INDIVIDAUAL and
CLIENT ACK modes, but my sample code fails in both cases.
Unit tests you pointed me out are unfortunately not relevant in this case,
because consumers t
I'm wondering if this is something I should worry about. I've noticed that
the error message has changed log level between releases 5.1 and 5.3 from
SEVERE to WARNING. But still, it's not acceptable on PROD environment.
jwotman wrote:
>
> I'm seeing the same exception. Using the
> org.apache.a
I'm getting following exception on broker side (5.3 and 5.1):
2009-11-11 21:12:25 org.apache.activemq.broker.TransportConnection
serviceException
WARNING: Async error occurred: javax.jms.JMSException: Could not correlate
acknowledgment with dispatched message: MessageAck {commandId = 14,
respons
