[gatein-issues] [JBoss JIRA] Created: (GTNPORTAL-474) Problem with IDM when same database is used for "portal" and "sample-portal"

[Marek Posolda (JIRA)]

Problem with IDM when same database is used for "portal" and "sample-portal"
----------------------------------------------------------------------------

                 Key: GTNPORTAL-474
                 URL: https://jira.jboss.org/jira/browse/GTNPORTAL-474
             Project: GateIn Portal
          Issue Type: Bug
         Environment: Ubuntu linux,
Sun JDK 1.6
GateIn from trunk (revision 1166) deployed on EAP 5.0.0.GA
            Reporter: Marek Posolda
             Fix For: 3.0.0-CR01


When same database is used for both portal containers "portal" and "sample-portal" in database-configuration.xml, then you can see error in server log during GateIn startup (or more precisely during startup of PicketLinkIDMOrganizationServiceImpl for Portal container "portal".) Because IDM transaction is not commited, users are not created for realm "portal" and then it's not possible to login to GateIn. 

By default each container has different database because database-confiuration.xml looks like this:

<property name="driverClassName" value="org.hsqldb.jdbcDriver"/>
<property name="url" value="jdbc:hsqldb:file:${gatein.db.data.dir}/data/exodb${container.name.suffix}"/>
<property name="username" value="sa"/>
<property name="password" value=""/>

Problem occurs when same DB is used for both containers, so URL looks like this:

<property name="url" value="jdbc:hsqldb:file:${gatein.db.data.dir}/data/exodb_shared"/>

Exception from server log is in attachement (idm-exception.txt).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira