I believe this is fixed on trunk. Can you try trunk?
I will do that (in our development area).
Is there anything that can be done to avoid the problem with 2.1.2.GA? If the selector failed and max-delivery-attempts worked, this would be a very minor issue.
trunk at the moment would be very equivalent to a 2.1.3.GA.. we just don't have resources to do it now. I believe the best would be to replace your current version with trunk.
Tim Fox fixed a bunch of Iterators on the redelivery loop. It sound this kind of scenario would be fixed by that.
At least give it a try and let us know how it goes.
I have have a version of the trunk built and the test environment switched over. However, the JMSBridge is having an issue getting a connection factory that is XA according to the stack trace. The JMSBridge kicks out the following error
14:48:05,519 WARNING [JMSBridgeImpl] Failed to connect bridge java.lang.IllegalArgumentException: Connection factory must be XAConnectionFactory at org.hornetq.jms.bridge.impl.JMSBridgeImpl.createConnection(JMSBridgeImpl.java:976) at org.hornetq.jms.bridge.impl.JMSBridgeImpl.setupJMSObjects(JMSBridgeImpl.java:1086)
True, but what will make it happy? Unfortunately the JMSBridge error messages do not provide to/from context to let you know which side it has issues with and the JNDI name of the object that is giving it the issue, hwoever I am currently trying to access the default XAConnectionFactory on both sides at this point.
+- XAConnectionFactory (class: org.hornetq.jms.client.HornetQJMSConnectionFactory) +- ConnectionFactory (class: org.hornetq.jms.client.HornetQJMSConnectionFactory)
This issue is new with my change to 2.2.0.CR1 - trunk
Hmmm... there's been a change which XA and NonXA connection are differentiated.
The XAConectionFactory in place here only has the XA as a name... let me look at how to deploy this...
Sorry for the hick up... let me look at this and I will get back shortly
I figured out enough to get running. The schema for hornetq-jms has changed. The xa-with-jta example slips in an "<xa>true</xa>" for the ConnectionFactory. Adding this to my cpnnection factories did the trick. My MDBs and @Stateless publishers, however, all use the default ConnectionFactory (internal), which has no xa=true property at the moment.
Tests are up and running.
yes.. that's it...
We will change the default configs as well
Things look more stable after 36hours of testing.
What is the forecast for a tagged CR1 release?
Original forecast was end of november.. but there are some clouds ahead :-) So... Dec 15th... with a GA early next year.
(That's still an estimate.. I'm not making any promises).
BTW: if stuff is working fine for you... the current state of trunk was something around what would have been 2.1.3. You could maybe write down the release you're using and keep using it until we get the release out.