Hi Ricardo,

We realized, after the release of XWiki 7.0 that due to our upgrade of DBCP to 
version 2.1 we’ve introduced a new requirement: JDBC 4 (I’m not sure if we 
require JDBC 4.0 or 4.1 actually, still trying to find out).  
See 
http://www.xwiki.org/xwiki/bin/view/ReleaseNotes/ReleaseNotesXWiki70#HIssuesspecifictoXWiki7.0
(http://www.xwiki.org/xwiki/bin/view/ReleaseNotes/ReleaseNotesXWiki70#HIssuesspecifictoXWiki7.0)
  

(http://www.xwiki.org/xwiki/bin/view/ReleaseNotes/ReleaseNotesXWiki70#HIssuesspecifictoXWiki7.0)
  
That said it seems that MySQL JDBC drivers 5.0.x are supposed to be JDBC4 
compliant and version 5.1.x certainly are too.

Thomas has just tested XWiki 7.0 on MySQL with version 5.1.28 and it was 
working fine for him.  

The error you get is strange. ATM I don’t understand it. We’re going to do more 
tests on various DBs to see whether we need to rollback the DBCP upgrade or not.

Stay tuned.

Sorry about the problem

Thanks
-Vincent

On 2 Apr 2015 at 09:39:45, [email protected] 
([email protected](mailto:[email protected]))
 wrote:

> Hi all!
>  
> We have successfuly updated our XWiki 6.x installation along the whole 6 
> cycle, but I'm in troubles with the new 7.0 release. I think that with only 
> the first four lines of the error stack
>  
> XWiki initialization failed !
>  
> Exception thrown during job execution
> class java.lang.AbstractMethodError: null
> at 
> org.apache.commons.dbcp2.DelegatingConnection.isValid(DelegatingConnection.java:914)
> at 
> org.apache.commons.dbcp2.DelegatingConnection.isValid(DelegatingConnection.java:914)
> ...
>  
> Here you could find all catalina.out logged me after a Tomcat shutdown/start 
> cycle and a call to XWiki in that server...
>  
> http://atriumkm.idisantiago.es/bin/download/ICT/XWikiUpgradeIssues/tomcatErrorLog.UpgradingTo70.txt
>  
>  
> XWiki is running in a CentOS box...
>  
> [root@idis1 /]# cat /etc/centos-release
> CentOS release 6.5 (Final)
>  
> With the following XWiki relevant pieces...
>  
> [root@idis1 /]# java -version
> *java version "1.8.0_11"
> Java(TM) SE Runtime Environment (build 1.8.0_11-b12)
> Java HotSpot(TM) 64-Bit Server VM (build 25.11-b03, mixed mode)
> ... concerning JDBC
> Since 1.7 -- new in the JDBC 4.1 API and part of the Java SE platform, 
> version 7
>  
> *INFO: Starting Servlet Engine: Apache Tomcat/7.0.55
> To the best of my knowledge, compatible with the new Servlet Spec as per...
> http://tomcat.apache.org/whichversion.html
> ... from XWiki 7.0 Release Notes
>  
> mysql> status
> --------------
> *mysql Ver 14.14 Distrib 5.5.38, for Linux (x86_64) using readline 5.1
>  
> *mysql-connector-java-5.0.8-bin.jar (2007-10-09)
> Well, this piece is a good candidate for being identified as the poblem, but 
> updating it to the last available release...
> mysql-connector-java-5.1.35-bin.jar (2015-03-23)
> ...doesn't solve the issue.
>  
>  
> As they are a lot of versions between mysql-connector-java-5.0.8-bin.jar 
> (working for us nicely so far) and the newest 
> mysql-connector-java-5.1.35-bin.jar (failing for us, at least with this 
> combination of Java, Tomcat and MySQL), please, could you tell us if we are 
> in the right direction? Should we update any other component but 
> mysql-connector-java-x.y.z-bin.jar to get XWiki 7.0 working? Should we start 
> trying one by one mysql-connector-java-x.y.z-bin.jar newer releases? Do you 
> know which release introduces JDBC 4.1 support?
>  
>  
> Thanks you so much for your help!
>  
> Ricardo

_______________________________________________
users mailing list
[email protected]
http://lists.xwiki.org/mailman/listinfo/users

Reply via email to