Thanks for reporting. You can find the latest changes on servicemix-jms at the following location: http://fisheye6.atlassian.com/changelog/servicemix/components/bindings/servicemix-jms/trunk What was the approximative date of the 36 build you are talking about ? Btw, the components version has changed, so it is now 2008.01-SNAPSHOT ...
On Sat, Sep 6, 2008 at 8:49 AM, Ryan Moquin <[EMAIL PROTECTED]> wrote: > Out of curiousity (I hate asking this), but I had upgraded from the 36 > version of 3.3-SNAPSHOT to the 46 one the other day. Every since then, my > servicemix-bean is back to locking up waiting for an exchange to process > with a servicemix-jms provider. It had definitely worked on the the 36 > build. So just in case I'm crazy, since I was the last time I asked about > this, and since I, go figure, didn't keep a 36 build I copy... I tried 48 > and 42, but neither work. When I deployed my same SAs on 3.2.2, all my > notifications started working again (figured even though they were built > against 3.3, might as well try it). Have there been any changes to > servicemix-jms in the last few builds? It's weird that it seems broken > now. If noone is sure, I think I can get a sample that works on 3.2.2 and > not 3.3. On monday, I can grab a copy of 36 build off our servers and try > that out again though I'm sure it will work since it does on 3.2.2, and I > don't want to touch any of my servicemix-client code so I don't make a > mistake like I did before. > > Let me know, if it seems like it's a bug (provided I'm not somehow crazy > again), then I'll try to get a sample created that shows it is a bug. If I > can get some time, I may just go and preemptively create the sample to show > it. For now I'll finish up what I was doing with 3.2.2 since that works. > > Ryan > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/
