The issue is that we have a number of existing applications that are deployed at various client sites that are currently using 4.0.2.
I'd like to move to 4.1 for one particular application and preferably for one particular client, to start with, to avoid me having to update all of the code and brokers everywhere in one big bang. I'll still have to branch the one application but I'm not expecting too many changes on that branch for the existing customer base. If I move all of the applications over to using a 4.1 client, I'll either have to branch everything or upgrade everyone's brokers. An example of what I'm aiming for: Client A: App A (4.0.2), App B (4.0.2), App C (4.0.2), Broker (4.0.2) Client B: App A (4.0.2), App B (4.0.2), App C (4.1), Broker (4.1) The improvement I'd like to take advantage of is Pure JDBC Master / Slave. I'm assuming that 4.0.2 client should handle failover just fine. I've seen this before (but with TIBCO) so I'm guessing it's a general problem with Enterprise Middleware. You get all the advantages of a homogenous message bus but you can get stuck on a particular version pretty easily if the broker's aren't backwardly compatible. cheers, j. On 1/15/07, Christopher G. Stach II <[EMAIL PROTECTED]> wrote:
Jamie McCrindle wrote: > Thanks James, > > cheers, > j. > > On 1/15/07, James Strachan <[EMAIL PROTECTED]> wrote: >> Generally speeking, we switch to major version numbers when things are >> completely incompatible. So 3.x won't talk to 4.x etc. When we move >> in minor upgrades such as 4.0.x to 4.1.x then clients should still >> work on the 4.1.x broker; though there's always a little bit of risk >> that we missed something as we don't yet have an automatic integration >> test to ensure that every feature on a 4.0.x client works perfectly on >> a 4.1.x broker etc. >> >> >> On 1/15/07, Jamie McCrindle <[EMAIL PROTECTED]> wrote: >> > hi all, >> > >> > do all components / applications in a system always need to be >> > upgraded when moving to new versions of activemq? specifically, i'd >> > like to move to activemq 4.1.0 but we have some activemq 4.0.2 client >> > applications that i'd prefer to keep that way rather than doing a big >> > bang migrate. >> > >> > regards, >> > jamie. >> > >> >> >> -- >> >> James >> ------- >> http://radio.weblogs.com/0112098/ >> I'm curious as to why you may want to stick with an older client when it's likely that a lot of the improvements are actually on the client side. -- Christopher G. Stach II
