Have you copied your old persistence.xml file of modify the bundled one? Have you add mysql*.jar file to the libraries?
To be fair I never saw such error :( Maybe longer stack trace will help .... On Thu, Apr 17, 2014 at 8:52 AM, Rob Foree <[email protected]> wrote: > Sorry, in checking my post I see I got the wrong persistant.xml, the > correct one has the mysql user name and password that was granted > permissions for the database whose name is open30 and a url which points to > the database created for this instance which looks like the following > > Url=jdbc:mysql://localhost:3306/open30?autoR..... > > Thanks > > > On Wed, Apr 16, 2014 at 8:44 PM, Rob Foree <[email protected]> wrote: > >> Hi, >> >> I am working on Centos 6x. >> I installed OM v2.2 and connected it to mysql according to directions I >> found on Tutorials+for+installing+OpenMeetings+and+Tools / >> the newest being "Installation of OpenMeetings 2.x and 3.x in CentOS >> 6.5.pdf" >> >> all went perfectly >> >> I then installed OM v3.00 following the same directions, only changing >> directory and database names. >> >> I get the following error, but NOT being a spring bean, I don't no how to >> proceed, nor am I sure I am providing the information you need to assist. >> >> ERROR 04-17 01:29:54.662 ScopeApplicationAdapter.java 11527 150 >> org.apache.openmeetings.remote.red5.ScopeApplicationAdapter >> [Launcher:/openmeetings] - [appStart] >> org.springframework.transaction.CannotCreateTransactionException: Could >> not open JPA EntityManager for transaction; >> nested exception is <openjpa-2.2.2-r422266:1468616 fatal user error> >> org.apache.openjpa.persistence.ArgumentException: >> The persistence provider is attempting to use properties in the >> persistence.xml file to resolve the data source. >> A Java Database Connectivity (JDBC) driver or data source class name must >> be specified in the openjpa.ConnectionDriverName or >> javax.persistence.jdbc.driver property. >> The following properties are available in the configuration: >> "org.apache.openjpa.jdbc.conf.JDBCConfigurationImpl@442ce698". >> >> the persistence.xml looks (partley) like this >> >> <properties> >> <property name="openjpa.RuntimeUnenhancedClasses" >> value="unsupported" /> >> <property name="openjpa.ConnectionDriverName" >> value="org.apache.commons.dbcp.BasicDataSource" /> >> <property name="openjpa.ConnectionProperties" >> >> value="DriverClassName=com.mysql.jdbc.Driver >> , >> Url=jdbc:mysql://localhost:3306/openmeetings?autoReconnect=true&useUnicode=true&createDatabaseIfNotExist=true&characterEncoding=utf-8&connectionCollation=utf8_general_ci&cachePrepStmts=true&cacheCallableStatements=true&cacheServerConfiguration=true&useLocalSessionState=true&elideSetAutoCommits=true&alwaysSendSetIsolation=false&enableQueryTimeouts=false&prepStmtCacheSize=3000&prepStmtCacheSqlLimit=1000 >> , MaxActive=100 >> , MaxWait=10000 >> , TestOnBorrow=true >> , poolPreparedStatements=true >> , Username=root >> , Password=" /> >> <property name="openjpa.jdbc.SynchronizeMappings" >> value="buildSchema" /> >> <property name="openjpa.Log" >> value="DefaultLevel=WARN, Runtime=INFO" /> >> <property name="openjpa.DataCache" value="true" /> >> <!-- QueryCache disabled due to changes outside >> of JPA doesn't take effect with caching --> >> <property name="openjpa.QueryCache" value="false" >> /> >> <property name="openjpa.jdbc.DBDictionary" >> value="batchLimit=100" /> >> <property name="openjpa.jdbc.QuerySQLCache" >> value="false" /> >> </properties> >> >> >> >> > -- WBR Maxim aka solomax
