Aaron,
We have a very similar issue in ServiceMix 3.3
(https://issues.apache.org/activemq/browse/SM-1438). I just wonder if
we need to change something in the way we address ActiveMQ to handle
these new types of MessageAck being used.
Regards,
Gert
Aaron Mulder wrote:
When I ran my examples including JMS against ActiveMQ 5.1.0, I got the
error below once (in the ActiveMQ console). I'm not sure what's up
with that, but I'm not sure it's a Camel problem. I would also need
to double-check the JARs on my classpath. But perhaps others could
try some basic JMS tests just to be sure?
Anyway, I'll vote +1 on the condition that the test JARs will be
released to the Maven repo even if they're not in the tarball. I
would prefer not to see a release where you have to build them from
source.
Thanks,
Aaron
ERROR Service - Async error occurred:
javax.jms.JMSException: Invalid acknowledgment: MessageAck {commandId
= 7, responseRequired = false, ackType = 3, consumerId =
ID:hagrid.local-65063-1215874089356-0:0:1:1, firstMessageId = null,
lastMessageId = ID:hagrid.local-65084-1215874104569-0:0:1:1:1,
destination = topic://SpringTest, transactionId = null, messageCount =
1}
javax.jms.JMSException: Invalid acknowledgment: MessageAck {commandId
= 7, responseRequired = false, ackType = 3, consumerId =
ID:hagrid.local-65063-1215874089356-0:0:1:1, firstMessageId = null,
lastMessageId = ID:hagrid.local-65084-1215874104569-0:0:1:1:1,
destination = topic://SpringTest, transactionId = null, messageCount =
1}
at
org.apache.activemq.broker.region.TopicSubscription.acknowledge(TopicSubscription.java:216)
at
org.apache.activemq.broker.region.AbstractRegion.acknowledge(AbstractRegion.java:364)
at
org.apache.activemq.broker.region.RegionBroker.acknowledge(RegionBroker.java:470)
at
org.apache.activemq.broker.TransactionBroker.acknowledge(TransactionBroker.java:194)
at
org.apache.activemq.broker.BrokerFilter.acknowledge(BrokerFilter.java:73)
at
org.apache.activemq.broker.BrokerFilter.acknowledge(BrokerFilter.java:73)
at
org.apache.activemq.broker.MutableBrokerFilter.acknowledge(MutableBrokerFilter.java:84)
at
org.apache.activemq.broker.TransportConnection.processMessageAck(TransportConnection.java:443)
at org.apache.activemq.command.MessageAck.visit(MessageAck.java:196)
at
org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:292)
at
org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:180)
at
org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.java:68)
at
org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:143)
at
org.apache.activemq.transport.InactivityMonitor.onCommand(InactivityMonitor.java:206)
at
org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:84)
at
org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:196)
at
org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:183)
at java.lang.Thread.run(Thread.java:613)
On Fri, Jul 11, 2008 at 11:02 PM, Hadrian Zbarcea <[EMAIL PROTECTED]> wrote:
This is a vote to release camel 1.4
A new Camel 1.4 is ready. Another fantastic community effort with 231
issues fixed.
Many thanks for all the hard work!
The staging area is at:
http://people.apache.org/~hadrian/apache-camel-1.4.0-RC3/maven2
The tarballs are here:
http://people.apache.org/~hadrian/apache-camel-1.4.0-RC3/maven2/org/apache/camel/apache-camel/1.4.0/
Please vote to approve this release binary. The vote will be open for at
least 72 hours.
[ ] +1 Release the binary as Apache Camel 1.4.0
[ ] -1 Veto the release (provide specific comments)
Here's my +1
Hadrian
