Hi Robert, If the JDBC-Driver is backwards compatible, than there shouldn't be an INFO Log Entry for every write/read that is done. My Log is spammed with
2007-10-18 10:31:03,349 INFO controller.core.Controller Old driver version is connecting (Driver=8.11, Controller=8.12) - some new features may not be accessible I know i can supress this with the log4j.properties, but i dont want to muss other INFO's from the controller. So i suggest to downgrade it to DEBUG, or add some logic, that this entry is only shown once and maybe as WARN. Can we start a vote on this issue? Thanx in advance Stefan Robert Hodges wrote: > Hi Stefan, > > It is our intention that Sequoia drivers will always be backwards > compatible so that you can do rolling upgrades without taking the full > cluster off-line. In the last year I think that has generally > worked--I can only recall one case where we broke compatibility. We > don't have any big plans for changes at this point to the drivers, so > it should not be too challenging to hold to this promise. > > Also, we will make an effort to avoid JMX changes that break rolling > upgrades, though as someone else just discovered you may need to > upgrade to the latest console for things to work properly. > > Cheers, Robert > > Robert Hodges, CTO, Continuent, Inc. > Email: [EMAIL PROTECTED] > Mobile: +1-510-501-3728 Skype: hodgesrm > > p.s., Off-topic but thanks for your email yesterday. > > > On Sep 7, 2007, at 2:15 AM, Stefan Lischke wrote: > >> Hi, >> >> just a short question about compatibility of the Sequoia JDBC driver. >> Will future versions of Sequoia work with clients that use an old >> sequoia-driver (for example 2.10.5)? Or do i have to update the sequoia >> jdc driver if i update sequoia? >> >> thanx in advance >> >> Stefan >>
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Sequoia mailing list [email protected] https://forge.continuent.org/mailman/listinfo/sequoia
