[gatein-issues] [JBoss JIRA] Created: (GTNPORTAL-503) javax.jcr.RepositoryException when same database used for both portal containers "portal" and "sample-portal"

[Marek Posolda (JIRA)]

javax.jcr.RepositoryException when same database used for both portal containers "portal" and "sample-portal"
-------------------------------------------------------------------------------------------------------------

                 Key: GTNPORTAL-503
                 URL: https://jira.jboss.org/jira/browse/GTNPORTAL-503
             Project: GateIn Portal
          Issue Type: Bug
         Environment: Ubuntu linux,
Sun JDK 1.6,
EAP 5 with GateIn from trunk (revision 1252)
            Reporter: Marek Posolda
         Attachments: database-configuration.xml

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. I've seeen this in server.log during GateIn startup:

16:00:07,014 ERROR [NodeIndexer] Binary value indexer error javax.jcr.RepositoryException: /home/mposolda/tmp/eap5-gatein-rev1252-examples/server/default/data/gatein/jcr/values/portal-system_portal/2/d/5/9/2/8/2/a7f000001006d707191522de0/2d59282a7f000001006d707191522de00 (No such file or directory): /home/mposolda/tmp/eap5-gatein-rev1252-examples/server/default/data/gatein/jcr/values/portal-system_portal/2/d/5/9/2/8/2/a7f000001006d707191522de0/2d59282a7f000001006d707191522de00 (No such file or directory)
javax.jcr.RepositoryException: /home/mposolda/tmp/eap5-gatein-rev1252-examples/server/default/data/gatein/jcr/values/portal-system_portal/2/d/5/9/2/8/2/a7f000001006d707191522de0/2d59282a7f000001006d707191522de00 (No such file or directory): /home/mposolda/tmp/eap5-gatein-rev1252-examples/server/default/data/gatein/jcr/values/portal-system_portal/2/d/5/9/2/8/2/a7f000001006d707191522de0/2d59282a7f000001006d707191522de00 (No such file or directory)
	at org.exoplatform.services.jcr.impl.storage.jdbc.JDBCStorageConnection.getItemByName(JDBCStorageConnection.java:804)
	at org.exoplatform.services.jcr.impl.storage.jdbc.JDBCStorageConnection.getItemData(JDBCStorageConnection.java:690)
	at org.exoplatform.services.jcr.impl.dataflow.persistent.WorkspacePersistentDataManager.getItemData(WorkspacePersistentDataManager.java:599)
	at org.exoplatform.services.jcr.impl.dataflow.persistent.CacheableWorkspaceDataManager.getPersistedItemData(CacheableWorkspaceDataManager.java:519)
	at org.exoplatform.services.jcr.impl.dataflow.persistent.CacheableWorkspaceDataManager.getItemData(CacheableWorkspaceDataManager.java:297)

By default each container has different database because database-configuration.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"/>

I believe that it should be possible to use same DB for both portal containers without any exceptions in server.log. Right now, there is similar issue GTNPORTAL-474 , which addresses exceptions with picketlink idm. So I am using database-configuration.xml from attachement where DB is shared only for JCR and not for picketlink. And with this configuration, I am seeing only JCR exceptions.

My database-configuration is in attachement as well as my server.log.

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