I am fairly certain that this is fixed. The stack trace attached earlier in this thread contains the following line which tells me that the code running does *not* contain the fix for SM-1171
org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlow.java:170) This line was where the previous exception occured and in the fixed code this line is the try block. I'm not sure why you couldn't see the fix for this but I committed it on April 2, 2008 in both trunk and the 3.2 branch and it appears in the Fisheye and Subversion commits tabs for the issue here https://issues.apache.org/activemq/browse/SM-1171 I'm going to go ahead and close this issue again so that we can get 3.2.2 released soon. Thanks, Chris On Mon, May 19, 2008 at 5:05 AM, Guillaume Nodet <[EMAIL PROTECTED]> wrote: > Could you create a simple junit test against trunk or 3.2 branch and > attach it to > a JIRA ? It would make it much easier for us to debug the problem ? > > On Mon, May 19, 2008 at 12:02 PM, n cardinale <[EMAIL PROTECTED]> > wrote: > > > > > > n cardinale wrote: > >> > >> Hello Chris, > >> > >> I built the servicemix 3.2.2 from a svn branch (3.2.2) got end of april. > I > >> checked in the source code: the fix done for SM-1171 is in this code > >> (file: AbstractFlow.java). > >> > >> Regards, > >> Nelly > >> > > > > -- > > View this message in context: > http://www.nabble.com/With-ServiceMix-3.2.2%2C-my-BeanEndpoint-can-still-receive-messages-before-it-has-fully-started%2C-same-as-SM-1171.-tp17204292p17315166.html > > Sent from the ServiceMix - User mailing list archive at Nabble.com. > > > > > > > > -- > Cheers, > Guillaume Nodet > ------------------------ > Blog: http://gnodet.blogspot.com/ > -- Chris Custine My Blog :: http://blog.organicelement.com Apache ServiceMix :: http://servicemix.apache.org Apache Directory Server :: http://directory.apache.org
