You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@openmeetings.apache.org by "Varga Balazs (JIRA)" <ji...@apache.org> on 2013/04/08 17:23:15 UTC

[jira] [Created] (OPENMEETINGS-605) Installation break, SQL error

Varga Balazs created OPENMEETINGS-605:
-----------------------------------------

             Summary: Installation break, SQL error
                 Key: OPENMEETINGS-605
                 URL: https://issues.apache.org/jira/browse/OPENMEETINGS-605
             Project: Openmeetings
          Issue Type: Bug
          Components: BuildsAndReleases
    Affects Versions: 3.0.0 Apache Release
            Reporter: Varga Balazs
            Assignee: SebastianWagner


I try installing OM 3.0.0 from https://builds.apache.org/job/openmeetings/433/

(try src and bin version)

The first install is broken many SQL faults: 
(full logs here: http://195.56.44.167:8080/openmeetings/log/3.0.0/433/

2013-04-08 17:15:01,599 [main] ERROR org.apache.openmeetings.cli.Admin - Install failed
org.springframework.transaction.CannotCreateTransactionException: Could not open JPA EntityManager for transaction; nested exception is <openjpa-2.2.1-r422266:1396819 nonfatal general error> org.apache.openjpa.persistence.PersistenceException: Incorrect table definition; there can be only one auto column and it must be defined as a key {stmnt 891348816 ALTER TABLE appointmentcategory ADD id BIGINT AUTO_INCREMENT} [code=1075, state=42000]
......
Incorrect table definition; there can be only one auto column and it must be defined as a key {stmnt 891348816 ALTER TABLE appointmentcategory ADD id BIGINT AUTO_INCREMENT} [code=1075, state=42000]


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira