Could you please re-create database using following SQL and try again

CREATE DATABASE openmeetings DEFAULT CHARACTER SET utf8 COLLATE
utf8_general_ci;

In case it wouldn't help I can create additional limitation on the length
of this field


On 4 June 2014 20:49, [heureka] Ulrich Huber <ulrich.hu...@heureka.co.at>
wrote:

>
>
>
>
> *Von:* Maxim Solodovnik [mailto:solomax...@gmail.com]
> *Gesendet:* Mittwoch, 04. Juni 2014 15:17
> *An:* Openmeetings user-list
> *Betreff:* Re: AW: AW: Upgrade to 3.0.2
>
>
>
> Installed few hours ago using this command
>
> ./admin.sh -v -i -tz "Asia/Tehran" -email solomax...@gmail.com -group
> test -user admin
>
>
>
> Installation was successful
>
> Could you try it? (using your own email/timezone/group/user)
>
>
>
> *[[heureka] - Ulrich Huber] I dumped the database and created a fresh one.
> There are some other errors now – and only part of the tables was created
> (Ending with conferencelogtype…) *
>
>
>
> *[ERROR] [main] org.apache.openmeetings.cli.Admin - Install failed*
>
> *org.springframework.transaction.CannotCreateTransactionException: Could
> not open JPA EntityManager for transaction; nested exception is
> <openjpa-2.2.2-r422266:1468616 nonfatal general error>
> org.apache.openjpa.persistence.PersistenceException: Specified key was too
> long; max key length is 767 bytes {stmnt 1077451042 CREATE TABLE
> configuration (id BIGINT NOT NULL AUTO_INCREMENT, comment_field TEXT,
> conf_key VARCHAR(255), conf_value VARCHAR(255), deleted BIT, starttime
> DATETIME, updatetime DATETIME, user_id BIGINT, PRIMARY KEY (id), UNIQUE
> U_CNFGRTN_CONF_KEY (conf_key)) ENGINE = innodb} [code=1071, state=42000]*
>
> *        at
> org.springframework.orm.jpa.JpaTransactionManager.doBegin(JpaTransactionManager.java:427)
> ~[spring-orm-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]*
>
> *        at
> org.springframework.transaction.support.AbstractPlatformTransactionManager.getTransaction(AbstractPlatformTransactionManager.java:371)
> ~[spring-tx-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]*
>
> *        at
> org.springframework.transaction.interceptor.TransactionAspectSupport.createTransactionIfNecessary(TransactionAspectSupport.java:335)
> ~[spring-tx-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]*
>
> *        at
> org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:105)
> ~[spring-tx-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]*
>
> *        at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
> ~[spring-aop-3.1.1.RELEASE.jar:3.1.1.RELEASE]*
>
> *        at
> org.springframework.aop.framework.Cglib2AopProxy$DynamicAdvisedInterceptor.intercept(Cglib2AopProxy.java:622)
> ~[spring-aop-3.1.1.RELEASE.jar:3.1.1.RELEASE]*
>
> *        at
> org.apache.openmeetings.db.dao.basic.ConfigurationDao$$EnhancerByCGLIB$$d6fae816.getConfValue(<generated>)
> ~[com.springsource.net.sf.cglib-2.2.0.jar:na]*
>
> *        at
> org.apache.openmeetings.db.util.UserHelper.getMinPasswdLength(UserHelper.java:34)
> ~[openmeetings-db-3.0.1-RELEASE.jar:na]*
>
> *        at
> org.apache.openmeetings.db.util.UserHelper.invalidPassword(UserHelper.java:38)
> ~[openmeetings-db-3.0.1-RELEASE.jar:na]*
>
> *        at
> org.apache.openmeetings.cli.Admin.checkAdminDetails(Admin.java:546)
> [openmeetings-cli-3.0.1-RELEASE.jar:na]*
>
> *        at org.apache.openmeetings.cli.Admin.process(Admin.java:274)
> [openmeetings-cli-3.0.1-RELEASE.jar:na]*
>
> *        at org.apache.openmeetings.cli.Admin.main(Admin.java:625)
> [openmeetings-cli-3.0.1-RELEASE.jar:na]*
>
> *Caused by: org.apache.openjpa.persistence.PersistenceException: Specified
> key was too long; max key length is 767 bytes {stmnt 1077451042 CREATE
> TABLE configuration (id BIGINT NOT NULL AUTO_INCREMENT, comment_field TEXT,
> conf_key VARCHAR(255), conf_value VARCHAR(255), deleted BIT, starttime
> DATETIME, updatetime DATETIME, user_id BIGINT, PRIMARY KEY (id), UNIQUE
> U_CNFGRTN_CONF_KEY (conf_key)) ENGINE = innodb} [code=1071, state=42000]*
>
> *        at
> org.apache.openjpa.jdbc.meta.MappingTool.record(MappingTool.java:559)
> ~[openjpa-bundle-2.2.2.jar:2.2.2]*
>
> *        at
> org.apache.openjpa.jdbc.meta.MappingTool.record(MappingTool.java:455)
> ~[openjpa-bundle-2.2.2.jar:2.2.2]*
>
> *        at
> org.apache.openjpa.jdbc.kernel.JDBCBrokerFactory.synchronizeMappings(JDBCBrokerFactory.java:160)
> ~[openjpa-bundle-2.2.2.jar:2.2.2]*
>
> *        at
> org.apache.openjpa.jdbc.kernel.JDBCBrokerFactory.synchronizeMappings(JDBCBrokerFactory.java:164)
> ~[openjpa-bundle-2.2.2.jar:2.2.2]*
>
> *        at
> org.apache.openjpa.jdbc.kernel.JDBCBrokerFactory.newBrokerImpl(JDBCBrokerFactory.java:122)
> ~[openjpa-bundle-2.2.2.jar:2.2.2]*
>
> *        at
> org.apache.openjpa.kernel.AbstractBrokerFactory.newBroker(AbstractBrokerFactory.java:209)
> ~[openjpa-bundle-2.2.2.jar:2.2.2]*
>
> *        at
> org.apache.openjpa.kernel.DelegatingBrokerFactory.newBroker(DelegatingBrokerFactory.java:156)
> ~[openjpa-bundle-2.2.2.jar:2.2.2]*
>
> *        at
> org.apache.openjpa.persistence.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:227)
> ~[openjpa-bundle-2.2.2.jar:2.2.2]*
>
> *        at
> org.apache.openjpa.persistence.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:154)
> ~[openjpa-bundle-2.2.2.jar:2.2.2]*
>
> *        at
> org.apache.openjpa.persistence.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:60)
> ~[openjpa-bundle-2.2.2.jar:2.2.2]*
>
> *        at
> org.springframework.orm.jpa.JpaTransactionManager.createEntityManagerForTransaction(JpaTransactionManager.java:445)
> ~[spring-orm-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]*
>
> *        at
> org.springframework.orm.jpa.JpaTransactionManager.doBegin(JpaTransactionManager.java:366)
> ~[spring-orm-jar-3.1.1.RELEASE.jar:3.1.1.RELEASE]*
>
> *        ... 11 common frames omitted*
>
> *Caused by: org.apache.openjpa.lib.jdbc.ReportingSQLException: Specified
> key was too long; max key length is 767 bytes {stmnt 1077451042 CREATE
> TABLE configuration (id BIGINT NOT NULL AUTO_INCREMENT, comment_field TEXT,
> conf_key VARCHAR(255), conf_value VARCHAR(255), deleted BIT, starttime
> DATETIME, updatetime DATETIME, user_id BIGINT, PRIMARY KEY (id), UNIQUE
> U_CNFGRTN_CONF_KEY (conf_key)) ENGINE = innodb} [code=1071, state=42000]*
>
> *        at
> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.wrap(LoggingConnectionDecorator.java:219)
> ~[openjpa-bundle-2.2.2.jar:2.2.2]*
>
> *        at
> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.wrap(LoggingConnectionDecorator.java:203)
> ~[openjpa-bundle-2.2.2.jar:2.2.2]*
>
> *        at
> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.access$700(LoggingConnectionDecorator.java:59)
> ~[openjpa-bundle-2.2.2.jar:2.2.2]*
>
> *        at
> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator$LoggingConnection$LoggingStatement.executeUpdate(LoggingConnectionDecorator.java:914)
> ~[openjpa-bundle-2.2.2.jar:2.2.2]*
>
> *        at
> org.apache.openjpa.lib.jdbc.DelegatingStatement.executeUpdate(DelegatingStatement.java:118)
> ~[openjpa-bundle-2.2.2.jar:2.2.2]*
>
> *        at
> org.apache.openjpa.jdbc.schema.SchemaTool.executeSQL(SchemaTool.java:1224)
> ~[openjpa-bundle-2.2.2.jar:2.2.2]*
>
> *        at
> org.apache.openjpa.jdbc.schema.SchemaTool.createTable(SchemaTool.java:975)
> ~[openjpa-bundle-2.2.2.jar:2.2.2]*
>
> *        at
> org.apache.openjpa.jdbc.schema.SchemaTool.add(SchemaTool.java:551)
> ~[openjpa-bundle-2.2.2.jar:2.2.2]*
>
> *        at
> org.apache.openjpa.jdbc.schema.SchemaTool.add(SchemaTool.java:366)
> ~[openjpa-bundle-2.2.2.jar:2.2.2]*
>
> *        at
> org.apache.openjpa.jdbc.schema.SchemaTool.run(SchemaTool.java:343)
> ~[openjpa-bundle-2.2.2.jar:2.2.2]*
>
> *        at
> org.apache.openjpa.jdbc.meta.MappingTool.record(MappingTool.java:505)
> ~[openjpa-bundle-2.2.2.jar:2.2.2]*
>
> *        ... 22 common frames omitted*
>
>
>
> On 4 June 2014 19:17, Vasiliy Degtyarev <va...@unipro.ru> wrote:
>
> I will try to check this error tomorrow.
>
> Thanks,
> Vasiliy
>
>
>
>
>
> On 04.06.2014 19:10, [heureka] Ulrich Huber wrote:
>
>
>
>
>
> *Von:* Vasiliy Degtyarev [mailto:va...@unipro.ru <va...@unipro.ru>]
> *Gesendet:* Mittwoch, 04. Juni 2014 14:05
> *An:* user@openmeetings.apache.org
> *Betreff:* Re: AW: Upgrade to 3.0.2
>
>
>
> What codepage you use for om database?
>
> *[[heureka] - Ulrich Huber] utf8_general_ci*
>
>
>
> On 04.06.2014 19:01, [heureka] Ulrich Huber wrote:
>
>
>
>
>
> *Von:* Vasiliy Degtyarev [mailto:va...@unipro.ru <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.convertJpaAccessExceptionIfPossible(EntityManagerFactoryUtils.java:326)
>
>         at
> org.springframework.orm.jpa.DefaultJpaDialect.translateExceptionIfPossible(DefaultJpaDialect.java:120)
>
>         at
> org.springframework.orm.jpa.JpaTransactionManager.doCommit(JpaTransactionManager.java:516)
>
>         at
> org.springframework.transaction.support.AbstractPlatformTransactionManager.processCommit(AbstractPlatformTransactionManager.java:754)
>
>         at
> org.springframework.transaction.support.AbstractPlatformTransactionManager.commit(AbstractPlatformTransactionManager.java:723)
>
>         at
> org.springframework.transaction.interceptor.TransactionAspectSupport.commitTransactionAfterReturning(TransactionAspectSupport.java:393)
>
>         at
> org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:120)
>
>         at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
>
>         at
> org.springframework.aop.framework.Cglib2AopProxy$DynamicAdvisedInterceptor.intercept(Cglib2AopProxy.java:622)
>
>         at
> org.apache.openmeetings.db.dao.basic.ConfigurationDao$$EnhancerByCGLIB$$fcc723cb.add(<generated>)
>
>         at
> org.apache.openmeetings.installation.ImportInitvalues.loadConfiguration(ImportInitvalues.java:365)
>
>         at
> org.apache.openmeetings.installation.ImportInitvalues.loadSystem(ImportInitvalues.java:985)
>
>         at
> org.apache.openmeetings.installation.ImportInitvalues.loadAll(ImportInitvalues.java:997)
>
>         at
> org.apache.openmeetings.web.pages.install.InstallWizard$InstallProcess.run(InstallWizard.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.java: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.java:570)
>
>         at
> org.springframework.orm.jpa.JpaTransactionManager.doCommit(JpaTransactionManager.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(PreparedStatementManagerImpl.java:144)
>
>         at
> org.apache.openjpa.jdbc.kernel.BatchingPreparedStatementManagerImpl.flushAndUpdate(BatchingPreparedStatementManagerImpl.java:79)
>
>         at
> org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.flushInternal(PreparedStatementManagerImpl.java:100)
>
>         at
> org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.flush(PreparedStatementManagerImpl.java:88)
>
>         at
> org.apache.openjpa.jdbc.kernel.ConstraintUpdateManager.flush(ConstraintUpdateManager.java:550)
>
>         at
> org.apache.openjpa.jdbc.kernel.ConstraintUpdateManager.flush(ConstraintUpdateManager.java:106)
>
>         at
> org.apache.openjpa.jdbc.kernel.BatchingConstraintUpdateManager.flush(BatchingConstraintUpdateManager.java:59)
>
>         at
> org.apache.openjpa.jdbc.kernel.AbstractUpdateManager.flush(AbstractUpdateManager.java:105)
>
>         at
> org.apache.openjpa.jdbc.kernel.AbstractUpdateManager.flush(AbstractUpdateManager.java:78)
>
>         at
> org.apache.openjpa.jdbc.kernel.JDBCStoreManager.flush(JDBCStoreManager.java:732)
>
>         at
> org.apache.openjpa.kernel.DelegatingStoreManager.flush(DelegatingStoreManager.java:131)
>
>         at
> org.apache.openjpa.datacache.DataCacheStoreManager.flush(DataCacheStoreManager.java:661)
>
>         at
> org.apache.openjpa.kernel.DelegatingStoreManager.flush(DelegatingStoreManager.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(LoggingConnectionDecorator.java:219)
>
>         at
> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.wrap(LoggingConnectionDecorator.java:195)
>
>         at
> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.access$1000(LoggingConnectionDecorator.java:59)
>
>         at
> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator$LoggingConnection$LoggingPreparedStatement.executeUpdate(LoggingConnectionDecorator.java:1134)
>
>         at
> org.apache.openjpa.lib.jdbc.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:275)
>
>         at
> org.apache.openjpa.lib.jdbc.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:275)
>
>         at
> org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.executeUpdate(PreparedStatementManagerImpl.java:268)
>
>         at
> org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.flushAndUpdate(PreparedStatementManagerImpl.java:119)
>
>         ... 32 more
>
>
>
>
>
> Any idea?
>
>
>
>
>
>
>
>
>
>
>
> --
> WBR
> Maxim aka solomax
>



-- 
WBR
Maxim aka solomax

Reply via email to