Re: Kaha corruption in 5.4-SNAPSHOT

I'm getting the same issue with the release version of 5.4.0. Deleting the db.data avoids the problem, however, I would like to have the recovery happen automatically without having to manually delete this file. Is there a way to achieve this? ripienaar wrote: > > > > Gary Tully wrote: >> >>

Re: prefetchExtension off-by-1 for transacted consumers with prefetchSize > 0

wanted to know if there are plans. Thx! rodos77 wrote: > > Ok, I have to finish some work first but I'll see how much I can get done > after that. I'm not too familiar with the classes you mentioned but I'll > see what I can figure out. > > In principle, I c

Re: prefetchExtension off-by-1 for transacted consumers with prefetchSize > 0

ated from the client. See how you get on. > > Otherwise, we can try and get this change into the 5.4 release. > > BTW: Is there a problem with the activemq RA that stops you from using it? > > > On 22 March 2010 14:56, rodos77 wrote: > >> >> I would point out

Re: prefetchExtension off-by-1 for transacted consumers with prefetchSize > 0

abled in the event that large transactions hang. > Thinking more, off by default is probably the best approach as > transactions > that exceed the prefetch should be rare and the RAR behavior would match > expectations. > > On 18 March 2010 22:05, rodos77 wrote: > >>

Re: prefetchExtension off-by-1 for transacted consumers with prefetchSize > 0

single transaction. Without the extension, the broker would see a full > prefetch and not dispatch any more and a receive could block. > > On 15 March 2010 21:31, rodos77 wrote: > >> >> JIRA AMQ-2651 opened. >> >> I would be happy to provide a patch but

Re: Messages lost when ServerSessionPool.getServerSession() throws a JMSException

JIRA AMQ-2653 created: https://issues.apache.org/activemq/browse/AMQ-2653 https://issues.apache.org/activemq/browse/AMQ-2653 -- View this message in context: http://old.nabble.com/Messages-lost-when-ServerSessionPool.getServerSession%28%29-throws-a-JMSException-tp27871597p27910865.html Sent fr

Re: ActiveMQ non-conformance to JMS Spec causing deadlock when using 3rd-party Resource Adapter

JIRA AMQ-2652 created: https://issues.apache.org/activemq/browse/AMQ-2652 https://issues.apache.org/activemq/browse/AMQ-2652 -- View this message in context: http://old.nabble.com/ActiveMQ-non-conformance-to-JMS-Spec-causing-deadlock-when-using-3rd-party-Resource-Adapter-tp27869447p27910830.h

Re: prefetchExtension off-by-1 for transacted consumers with prefetchSize > 0

JIRA AMQ-2651 opened. I would be happy to provide a patch but as I stated in my original post, I don't fully understand the need for prefetchExtension in the case of a transacted, asynchronous (prefetchSize > 0) consumer. If somebody could explain it, that would perhaps give me the required know

Re: prefetchExtension off-by-1 for transacted consumers with prefetchSize > 0

Any responses to this or the other 2 issues I posted ? I think these are pretty serious issues. If I'm correct, this makes AMQ non compliant to the JMS Spec. I've gone through the trouble of designing a test for each issue so it should be very easy to verify the problem. Do I need to open some

Messages lost when ServerSessionPool.getServerSession() throws a JMSException

In ActiveMQConnectionConsumer.dispatch() method, if the call to sessionPool.getServerSession() results in an Exception, the message being dispatched is never redelivered and is lost forever. In fact, it gets stuck in the dispatch queue and can result in no new messages at all being delivered to t

ActiveMQ non-conformance to JMS Spec causing deadlock when using 3rd-party Resource Adapter

The following is an excerpt from the JMS Spec 1.1: 8.2.3 ServerSessionPool .. If the ServerSessionPool is out of ServerSessions, the getServerSession() method may block. If a ConnectionConsumer is blocked, it cannot deliver new messages until a ServerSession

prefetchExtension off-by-1 for transacted consumers with prefetchSize > 0

Hi, I've searched the forum and JIRA and have noticed that the prefetchExtension in PrefetchSubscription has caused grief before. However, I think there still a problem. First, I understand the purpose of the prefetchExtension for the case when prefetchSize = 0. It allows messages to be dispat