You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@syncope.apache.org by "Nik Tetteh-Lartey (JIRA)" <ji...@apache.org> on 2013/05/28 17:34:21 UTC

[jira] [Created] (SYNCOPE-375) QUARTZ tables are not written into an innodb mysql DB for an mvn generated and created project

Nik Tetteh-Lartey created SYNCOPE-375:
-----------------------------------------

             Summary: QUARTZ tables are not written into an innodb mysql DB for an mvn generated and created project
                 Key: SYNCOPE-375
                 URL: https://issues.apache.org/jira/browse/SYNCOPE-375
             Project: Syncope
          Issue Type: Bug
          Components: core
    Affects Versions: 1.1.2
         Environment: linux fedora 17 Fedora release 17 (Beefy Miracle)
and
Mac OSX Mountain lion

            Reporter: Nik Tetteh-Lartey
            Priority: Blocker


building a snapshot 1.1.2 project (as per the wiki) and deploying the war file on a glassfish container using
a mysql DB as persistant storage (re: wiki) results in a target DB being built with any of the QUARTZ tables used by syncope idm.

WORK AROUND:
1. drop and create again (or just make empty) with current MySQL database
2. download attached file, save it under core/src/main/resources/quartz/ (create required paths required)
3. rebuild and redeploy
4. verify Quartz tables are now created as follows:
bash-4.1# mysql -uroot -pwelcome  syncope -A
:
mysql> show tables like 'QRTZ%';
+---------------------------+
| Tables_in_syncope (QRTZ%) |
+---------------------------+
| QRTZ_BLOB_TRIGGERS        |
| QRTZ_CALENDARS            |
| QRTZ_CRON_TRIGGERS        |
| QRTZ_FIRED_TRIGGERS       |
| QRTZ_JOB_DETAILS          |
| QRTZ_LOCKS                |
| QRTZ_PAUSED_TRIGGER_GRPS  |
| QRTZ_SCHEDULER_STATE      |
| QRTZ_SIMPLE_TRIGGERS      |
| QRTZ_SIMPROP_TRIGGERS     |
| QRTZ_TRIGGERS             |
+---------------------------+
11 rows in set (0.00 sec)

mysql> 


--
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