0 Replies Latest reply: Feb 20, 2013 1:00 PM by johng RSS

    JDBC TX Settings for Weblogic Portal Content Repo Datasources

    johng
      I have a scenario where I require two WLP content stores for the application. If I set the individual datasources to Support Global Transactions = True, then the application throws TX errors: ...Caused by: java.sql.SQLException: Connection has already been created in this tx context for pool named PMRestDataSource. Illegal attempt to create connection from another pool: portalDataSource.

      What I did to solve this was isolate the Content Repo datasource from the portalDataSource (in fact, it is in a separate database schema from the portal framework artifacts in the Production environment), and set both of the Content-specific datasources to Support Global Transactions = False that fixed the issue.

      The question I have is this: Is there any reason I need TX support for datasources that exclusively support connecting to a WLP Content Store?

      Thanks in advance for your help!

      Reference content-config.xml:

      <content-store>
      <name>PM Repository</name>
      <description>Default Content Repository Configuration</description>
      <class-name>com.bea.content.spi.internal.ExtendedRepositoryImpl</class-name>
      <repository-property>
      <description>Data source to use.</description>
      <name>CM_DATA_SOURCE</name>
      <value>PMRepoDataSource</value>
      </repository-property>
      <repository-property>
      <description>Enable repository events for full-text search.</description>
      <name>cm_fireRepositoryEvents</name>
      <value>false</value>
      </repository-property>
      <read-only>false</read-only>
      <binary-cache-max-entry-size>1024</binary-cache-max-entry-size>
      <!-- metadata search -->
      <search-is-enabled>true</search-is-enabled>
      <!-- full text search -->
      <fulltext-search-is-enabled>true</fulltext-search-is-enabled>
      <search-indexing-is-enabled>true</search-indexing-is-enabled>
      </content-store>
      <content-store>
      <name>REST Repository</name>
      <description>REST Content Repository Configuration</description>
      <class-name>com.bea.content.spi.internal.ExtendedRepositoryImpl</class-name>
      <repository-property>
      <description>Data source to use.</description>
      <name>CM_DATA_SOURCE</name>
      <value>PMRestDataSource</value>
      </repository-property>
      <repository-property>
      <description>Enable repository events for full-text search.</description>
      <name>cm_fireRepositoryEvents</name>
      <value>false</value>
      </repository-property>
      <read-only>false</read-only>
      <binary-cache-max-entry-size>1024</binary-cache-max-entry-size>
      <!-- metadata search -->
      <search-is-enabled>true</search-is-enabled>
      <!-- full text search -->
      <fulltext-search-is-enabled>false</fulltext-search-is-enabled>
      <search-indexing-is-enabled>true</search-indexing-is-enabled>
      </content-store>