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

Sorin Sbarnea updated MRM-1881:
-------------------------------
    Attachment: logs.tar.gz

> Release 2.2.0 does not work with PostgreSQL
> -------------------------------------------
>
>                 Key: MRM-1881
>                 URL: https://issues.apache.org/jira/browse/MRM-1881
>             Project: Archiva
>          Issue Type: Bug
>          Components: Documentation
>    Affects Versions: 2.2.0
>         Environment: oracle-java-1.8, ubuntu-12.04-lts
>            Reporter: Sorin Sbarnea
>            Priority: Critical
>              Labels: postgresql
>         Attachments: logs.tar.gz
>
>
> It seems that support for PostgreSQL is broken and mostly undocumented.
> There a few things that need to be addressed:
> * Include PostgreSQL ODBC driver in the build, no need to keep it outside 
> only to make the installation harder. 
> * Include commented out PostreSQL database configuration inside 
> /conf/jetty.conf  including 
> {noformat}
> <New id="users" class="org.eclipse.jetty.plus.jndi.Resource">
>     <Arg>jdbc/users</Arg>
>     <Arg>
>       <New class="org.apache.tomcat.jdbc.pool.DataSource">
>         <Set name="driverClassName">org.postgresql.Driver</Set>
>         <Set name="url">jdbc:postgresql://localhost/archiva</Set>
>         <Set name="name">ArchivaApp</Set>
>         <Set name="username">archiva</Set>
>         <Set name="password">archivasecret</Set>
>         <!-- depends on your concurrent users numbers -->
>         <Set name="maxWait">10000</Set>
>         <Set name="removeAbandonedTimeout">10000</Set>
>         <Set name="maxActive">30</Set>
>         <Set name="initialSize">15</Set>
>         <Set name="removeAbandoned">true</Set>
>         <Set name="logAbandoned">true</Set>
>         <Set name="testOnBorrow">true</Set>
>         <!-- very rigourous sql query validation -->
>         <Set name="validationQuery">select 1</Set>
>         <Set name="testOnReturn">false</Set>
>         <!--<Set name="defaultTransactionIsolation">READ_COMMITTED</Set>-->
>       </New>
>     </Arg>
>   </New>
> {noformat}
> Also even with these changes being made it seems that Archiva is not properly 
> initialized. The database tables are created with the default admin account 
> but we cannot validate the admin account (email confirmation fails). We will 
> attach the logs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to