And I could implement this in JBC 2.1.0.GA easily enough, but if there is a viable workaround I'd rather leave this for 2.2.0 given current timeframes. On 4 Mar 2008, at 07:14, Bela Ban wrote: > > > Brian Stansberry wrote: >> Being able to handle this in JBC 2.1.0 is a bit more of an issue due >> to a bug in the way JBM handles a Channel.connect() call >> (http://jira.jboss.com/jira/browse/JBMESSAGING-1244). The bug >> basically means JBM will fail if it calls >> ChannelFactory.createMultiplexerChannel() and the call doesn't >> return a MuxChannel. So, my intended approach for AS 5 (override >> createMultiplexerChannel()and return a regular JChannel if it's >> configured for shared transport) breaks JBM. >> >> Maybe they'll get JBMESSAGING-1244 fixed in time for AS 5; maybe not. > > I certainly hope so, sounds like a small change (use a JChannel type > rather than a MuxChannel (extends JChannel))... > >> If we can get a JGroups 2.6.3 > > Another release, so soon after 2.6.2 ? Only if absolutely necessary. > Seems to me that Tim can fix his stuff much more quickly... In any > case, let me know, I need a few days to get a 2.6.3 out (including > fixing the NPE you opened). > >> and JBC 2.1.0.GA able to call ChannelFactory.createChannel(), then I >> can just let JBM get a MuxChannel. > > This is possible in 2.6.3 by which feature/bug I implemented ? > > -- > Bela Ban > Lead JGroups / Clustering Team > JBoss - a division of Red Hat -- Manik Surtani Lead, JBoss Cache manik(a)jboss.org msurtani(a)redhat.com