JCR - Enterprise Portal Platform 5

Locks changes

While JBoss Enterprise Portal Platform 5.2 offers new configuration options to configure the JCR, older scenarios are still supported. The way JCR stores locks has changed and may not let the migrated portal start.

To work around this you will need to start the portal once with the parameter -Dorg.exoplatform.jcr.locks.force.remove, instructions are:

Start the server with

Start the server

sh run.sh -Dorg.exoplatform.jcr.locks.force.remove

Stop the server
Start the server without the option

Datasource changes

Configuration changes has been made since the JCR can now reuse transactions managed by the application server. As a consequence the datasource used by JCR needs to be declared as <local-tx-datasource>:

Example

<datasources>
   <no-tx-datasource>
      <jndi-name>gatein-idm</jndi-name>
      <connection-url>jdbc:hsqldb:${jboss.server.data.dir}${/}gatein${/}hypersonic${/}gatein-idm-localDB</connection-url>
      <driver-class>org.hsqldb.jdbcDriver</driver-class>
      <user-name>sa</user-name>
      <password></password>

      <min-pool-size>5</min-pool-size>
      <max-pool-size>20</max-pool-size>
      <idle-timeout-minutes>0</idle-timeout-minutes>
      <prepared-statement-cache-size>32</prepared-statement-cache-size>
   </no-tx-datasource>
  
   <local-tx-datasource>
      <jndi-name>gatein-jcr</jndi-name>
      <connection-url>jdbc:hsqldb:${jboss.server.data.dir}${/}gatein${/}hypersonic${/}gatein-jcr-localDB</connection-url>
      <driver-class>org.hsqldb.jdbcDriver</driver-class>
      <user-name>sa</user-name>
      <password></password>

      <min-pool-size>5</min-pool-size>
      <max-pool-size>20</max-pool-size>
      <idle-timeout-minutes>0</idle-timeout-minutes>
      <prepared-statement-cache-size>32</prepared-statement-cache-size>
   </local-tx-datasource>
</datasources>