Von: Vasiliy Degtyarev [mailto:va...@unipro.ru] 
Gesendet: Mittwoch, 04. Juni 2014 13:49
An: user@openmeetings.apache.org
Betreff: Re: Upgrade to 3.0.2

 

What command you use to create openmeetings database?



[[heureka] - Ulrich Huber] I created it using phpmyadmin; user openmeetings
has full access (including grant) to the db openmeetings



On 04.06.2014 18:43, [heureka] Ulrich Huber wrote:

I was following the guide @ http://openmeetings.apache.org/Upgrade.html;
upgrade was recommended by maxim in order to address the generatingURL/mail
invitation-issue. 

 

At the end of the installation process, I got an error@
/openmeetings/install?6 (I dumped the databases and created a new one,
following the recommendations in the upgrade-guide.) 

 


Installation is failed

org.springframework.orm.jpa.JpaSystemException: The transaction has been
rolled back.  See the nested exceptions for details on the errors that
occurred.; nested exception is <openjpa-2.2.2-r422266:1468616 fatal general
error> org.apache.openjpa.persistence.PersistenceException: The transaction
has been rolled back.  See the nested exceptions for details on the errors
that occurred.

FailedObject: org.apache.openmeetings.db.entity.basic.Configuration@286a0559

        at
org.springframework.orm.jpa.EntityManagerFactoryUtils.convertJpaAccessExcept
ionIfPossible(EntityManagerFactoryUtils.java:326)

        at
org.springframework.orm.jpa.DefaultJpaDialect.translateExceptionIfPossible(D
efaultJpaDialect.java:120)

        at
org.springframework.orm.jpa.JpaTransactionManager.doCommit(JpaTransactionMan
ager.java:516)

        at
org.springframework.transaction.support.AbstractPlatformTransactionManager.p
rocessCommit(AbstractPlatformTransactionManager.java:754)

        at
org.springframework.transaction.support.AbstractPlatformTransactionManager.c
ommit(AbstractPlatformTransactionManager.java:723)

        at
org.springframework.transaction.interceptor.TransactionAspectSupport.commitT
ransactionAfterReturning(TransactionAspectSupport.java:393)

        at
org.springframework.transaction.interceptor.TransactionInterceptor.invoke(Tr
ansactionInterceptor.java:120)

        at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(Reflect
iveMethodInvocation.java:172)

        at
org.springframework.aop.framework.Cglib2AopProxy$DynamicAdvisedInterceptor.i
ntercept(Cglib2AopProxy.java:622)

        at
org.apache.openmeetings.db.dao.basic.ConfigurationDao$$EnhancerByCGLIB$$fcc7
23cb.add(<generated>)

        at
org.apache.openmeetings.installation.ImportInitvalues.loadConfiguration(Impo
rtInitvalues.java:365)

        at
org.apache.openmeetings.installation.ImportInitvalues.loadSystem(ImportInitv
alues.java:985)

        at
org.apache.openmeetings.installation.ImportInitvalues.loadAll(ImportInitvalu
es.java:997)

        at
org.apache.openmeetings.web.pages.install.InstallWizard$InstallProcess.run(I
nstallWizard.java:389)

        at java.lang.Thread.run(Thread.java:662)

Caused by: <openjpa-2.2.2-r422266:1468616 fatal general error>
org.apache.openjpa.persistence.PersistenceException: The transaction has
been rolled back.  See the nested exceptions for details on the errors that
occurred.

FailedObject: org.apache.openmeetings.db.entity.basic.Configuration@286a0559

        at
org.apache.openjpa.kernel.BrokerImpl.newFlushException(BrokerImpl.java:2347)

        at org.apache.openjpa.kernel.BrokerImpl.flush(BrokerImpl.java:2184)

        at
org.apache.openjpa.kernel.BrokerImpl.flushSafe(BrokerImpl.java:2082)

        at
org.apache.openjpa.kernel.BrokerImpl.beforeCompletion(BrokerImpl.java:2000)

        at
org.apache.openjpa.kernel.LocalManagedRuntime.commit(LocalManagedRuntime.jav
a:81)

        at org.apache.openjpa.kernel.BrokerImpl.commit(BrokerImpl.java:1524)

        at
org.apache.openjpa.kernel.DelegatingBroker.commit(DelegatingBroker.java:933)

        at
org.apache.openjpa.persistence.EntityManagerImpl.commit(EntityManagerImpl.ja
va:570)

        at
org.springframework.orm.jpa.JpaTransactionManager.doCommit(JpaTransactionMan
ager.java:512)

        ... 12 more

Caused by: <openjpa-2.2.2-r422266:1468616 fatal general error>
org.apache.openjpa.persistence.PersistenceException: Data truncation: Data
too long for column 'conf_value' at row 1 {prepstmnt 515643217 INSERT INTO
configuration (comment_field, conf_key, conf_value, deleted, starttime,
updatetime, user_id) VALUES (?, ?, ?, ?, ?, ?, ?)} [code=1406, state=22001]

FailedObject: org.apache.openmeetings.db.entity.basic.Configuration@286a0559

        at
org.apache.openjpa.jdbc.sql.DBDictionary.narrow(DBDictionary.java:4962)

        at
org.apache.openjpa.jdbc.sql.DBDictionary.newStoreException(DBDictionary.java
:4922)

        at
org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:136)

        at
org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:78)

        at
org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.flushAndUpdate(P
reparedStatementManagerImpl.java:144)

        at
org.apache.openjpa.jdbc.kernel.BatchingPreparedStatementManagerImpl.flushAnd
Update(BatchingPreparedStatementManagerImpl.java:79)

        at
org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.flushInternal(Pr
eparedStatementManagerImpl.java:100)

        at
org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.flush(PreparedSt
atementManagerImpl.java:88)

        at
org.apache.openjpa.jdbc.kernel.ConstraintUpdateManager.flush(ConstraintUpdat
eManager.java:550)

        at
org.apache.openjpa.jdbc.kernel.ConstraintUpdateManager.flush(ConstraintUpdat
eManager.java:106)

        at
org.apache.openjpa.jdbc.kernel.BatchingConstraintUpdateManager.flush(Batchin
gConstraintUpdateManager.java:59)

        at
org.apache.openjpa.jdbc.kernel.AbstractUpdateManager.flush(AbstractUpdateMan
ager.java:105)

        at
org.apache.openjpa.jdbc.kernel.AbstractUpdateManager.flush(AbstractUpdateMan
ager.java:78)

        at
org.apache.openjpa.jdbc.kernel.JDBCStoreManager.flush(JDBCStoreManager.java:
732)

        at
org.apache.openjpa.kernel.DelegatingStoreManager.flush(DelegatingStoreManage
r.java:131)

        at
org.apache.openjpa.datacache.DataCacheStoreManager.flush(DataCacheStoreManag
er.java:661)

        at
org.apache.openjpa.kernel.DelegatingStoreManager.flush(DelegatingStoreManage
r.java:131)

        ... 20 more

Caused by: org.apache.openjpa.lib.jdbc.ReportingSQLException: Data
truncation: Data too long for column 'conf_value' at row 1 {prepstmnt
515643217 INSERT INTO configuration (comment_field, conf_key, conf_value,
deleted, starttime, updatetime, user_id) VALUES (?, ?, ?, ?, ?, ?, ?)}
[code=1406, state=22001]

        at
org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.wrap(LoggingConnectio
nDecorator.java:219)

        at
org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.wrap(LoggingConnectio
nDecorator.java:195)

        at
org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.access$1000(LoggingCo
nnectionDecorator.java:59)

        at
org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator$LoggingConnection$Log
gingPreparedStatement.executeUpdate(LoggingConnectionDecorator.java:1134)

        at
org.apache.openjpa.lib.jdbc.DelegatingPreparedStatement.executeUpdate(Delega
tingPreparedStatement.java:275)

        at
org.apache.openjpa.lib.jdbc.DelegatingPreparedStatement.executeUpdate(Delega
tingPreparedStatement.java:275)

        at
org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.executeUpdate(Pr
eparedStatementManagerImpl.java:268)

        at
org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.flushAndUpdate(P
reparedStatementManagerImpl.java:119)

        ... 32 more

        

 

 

Any idea? 

 

Reply via email to