On Sat, Jul 11, 2009 at 1:26 AM, huntc<[email protected]> wrote: > > > Claus Ibsen-2 wrote: >> >> Are your routes InOnly? Eg you do not consume from a JMS queue? >> > > Yes I do have some in-only routes. Could the maxMessagesPerTask default > issue cause an unwieldily number of connections to be made with the broker?
This option is part of Spring JMS and could also be used/affect when sending only. So I advice to configure all your JMS endpoints in 1.6.1 with maxMessagesPerTask=-1 > > Also is there any feel for when 1.6.2 is out or better still 2.0? It is > probably time I got off the 1.x source base given 2.0 is probably where most > focus is nowadays. 1.6.x should be good enough for production usage. Out intention is of course to support it as good as we can and do important bug fixes. But out own focus and energy has been on 2.0 for quite a while now. I recommend to try out 2.0m2 or better yet 2.0 trunk when you got the time. Maybe giving your existing application a test drive with it. The more feedback we can get with X apps not working / working after a upgrade the better. But we picked up a recent discussion on some API changes for 2.0 so it would take another 1-2 weeks before a RC can be cut, as opposed to I was hoping the RC could have been cut this weekend. But anyway its feature complete. But the API is something we gotta cease the moment and mold before its GA. > -- > View this message in context: > http://www.nabble.com/JMS-publish-consuming-sockets--tp24401653p24435619.html > Sent from the Camel - Users (activemq) mailing list archive at Nabble.com. > > -- Claus Ibsen Apache Camel Committer Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/ Twitter: http://twitter.com/davsclaus
