[jira] [Updated] (OOZIE-1660) DB connection misconfig causes all or most unit tests to fail

["Robert Kanter (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/OOZIE-1660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Kanter updated OOZIE-1660:
---------------------------------

    Attachment: OOZIE-1660.patch

The patch sets {{oozie.service.JPAService.create.db.schema=true}} in XTestCase.  It also changes an inconsistent line in JPAService that I missed in OOZIE-1655.  

> DB connection misconfig causes all or most unit tests to fail
> -------------------------------------------------------------
>
>                 Key: OOZIE-1660
>                 URL: https://issues.apache.org/jira/browse/OOZIE-1660
>             Project: Oozie
>          Issue Type: Bug
>          Components: tests
>    Affects Versions: trunk
>            Reporter: Robert Kanter
>            Assignee: Robert Kanter
>            Priority: Blocker
>         Attachments: OOZIE-1660.patch
>
>
> OOZIE-1655 changed oozie-default’s {{oozie.service.JPAService.create.db.schema}} to match oozie-site by setting it to {{false}}.  This caused all or most unit tests to either fail with errors containing "{{Cannot create PoolableConnectionFactory}}" or to get stuck.  For the unit tests, we need to set the property to true so that it will create the database schema because we don't create it manually like during a regular deployment.  This was only working before because oozie-default and oozie-site were not in-sync.
> I'm not sure why test-patch in OOZIE-1655 didn't catch this or why I had to clone into a new folder to reproduce this locally either.  Perhaps we're not deleting the database when doing a {{mvn clean}}?



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)