OK. Figured it out. With Spring 2.x, the DefaultMessageListenerContainer that we create seems to be automatically started. We don't ever call start on it. With Spring 3, we need to call start(). If I add that call after the initialize, all the JMS tests pass.
Dan On Thu December 17 2009 5:17:52 pm Daniel Kulp wrote: > I added a profile to the build to build/run with the recently released > Spring 3. I have it completely building now (although a bunch of > warnings as Spring deprecated a bunch of stuff that we need to call for > Spring 2.5), however, the JMS tests are hanging. > > I would really appreciate it if someone could help look at it. Just run > > mvn -Pspring3 > > and it hangs in the JMSDestinationTest. It may just be a timeout or > something needing adjusting or similar. Don't really know yet. > > You can also run it in eclipse and see. A call like: > > mvn -Psetup.eclipse,spring3 > would setup the eclipse workspace with the spring3 jars. I can duplicate > the hang there as well. > -- Daniel Kulp dk...@apache.org http://www.dankulp.com/blog
