Foren
Problem by setting jndi jackrabbit with oracle (FileSystem)
Ricardo Martínez, geändert vor 12 Jahren.
Problem by setting jndi jackrabbit with oracle (FileSystem)
New Member Beiträge: 6 Beitrittsdatum: 27.05.10 Neueste Beiträge
I'm trying to configure the liferay bundle 6.0.6 with Jackrabbit through JNDI and after several tests Configuration using JNDI at FileSystem (removing the connection string jdbc / authentication and change by jndi fails with the following error):
In contrast to the repository. xml (whether it works correctly)
That problem exists with Jacrabbit and Oracle or where is the problem?
I tried to patch jackrabbit following some post, but without success, [url=https://issues.apache.org/jira/browse/JCR-1907?
page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel]JIRA-1907
I tested with the parameters jndi:
Throwing Error is: "jdbc not bound"
Has anyone encountered this?
Thanks and greetings to all!
2011-10-13 08:47:54,411 ERROR [org.apache.jackrabbit.core.RepositoryImpl] (main) failed to start Repository: failed to load repository properties: failed to persist repository properties: null
javax.jcr.RepositoryException: failed to load repository properties: failed to persist repository properties: null: failed to persist repository properties: null: null
In contrast to the repository. xml (whether it works correctly)
<!-- Repository Configuration File -->
<repository>
<!-- FILESYSTEM -->
<filesystem class="org.apache.jackrabbit.core.fs.db.OracleFileSystem">
<param name="driver" value="oracle.jdbc.driver.OracleDriver">
<param name="url" value="jdbc:oracle:thin:@xxx.xxx.xxx.xxx:1521:name">
<param name="user" value="qua">
<param name="password" value="qua">
<param name="schema" value="oracle">
<param name="schemaObjectPrefix" value="LR_FS_">
</filesystem>
<!-- SECURITY CONFIGURATION-->
<security appname="Jackrabbit">
<accessmanager class="org.apache.jackrabbit.core.security.SimpleAccessManager" />
<loginmodule class="org.apache.jackrabbit.core.security.SimpleLoginModule">
<param name="anonymousId" value="anonymous">
</loginmodule>
</security>
<!-- WORKSPACE location of workspaces root directory and name of default workspace -->
<workspaces rootPath="${rep.home}/workspaces" defaultWorkspace="liferay" />
<workspace name="Liferay">
<filesystem class="org.apache.jackrabbit.core.fs.db.OracleFileSystem">
<param name="driver" value="javax.naming.InitialContext">
<param name="url" value="java:jdbc/LiferayPool">
<param name="schema" value="oracle">
<param name="schemaObjectPrefix" value="LR_WS_FS_">
</filesystem>
<persistencemanager class="org.apache.jackrabbit.core.persistence.bundle.OraclePersistenceManager">
<param name="driver" value="javax.naming.InitialContext">
<param name="url" value="java:jdbc/LiferayPool">
<param name="schema" value="oracle">
<param name="schemaObjectPrefix" value="LR_WS_PM_">
<param name="externalBLOBs" value="false">
</persistencemanager>
</workspace>
<versioning rootpath="${rep.home}/version">
<!-- Uncomment to move to DB -->
<filesystem class="org.apache.jackrabbit.core.fs.db.OracleFileSystem">
<param name="driver" value="javax.naming.InitialContext">
<param name="url" value="java:jdbc/LiferayPool">
<param name="schema" value="oracle">
<param name="schemaObjectPrefix" value="LR_V_FS_">
</filesystem>
<persistencemanager class="org.apache.jackrabbit.core.persistence.bundle.OraclePersistenceManager">
<param name="driver" value="javax.naming.InitialContext">
<param name="url" value="java:jdbc/LiferayPool">
<param name="schema" value="oracle">
<param name="schemaObjectPrefix" value="LR_V_PM_">
<param name="externalBLOBs" value="false">
</persistencemanager>
</versioning>
<!-- Cluster Configuration -->
<!-- Uncomment to move to database -->
<cluster id="nodo1" syncdelay="2000">
<journal class="org.apache.jackrabbit.core.journal.OracleDatabaseJournal">
<param name="revision" value="${rep.home}/revision.log">
<param name="driver" value="javax.naming.InitialContext">
<param name="url" value="java:jdbc/LiferayPool">
<param name="schema" value="oracle">
<param name="schemaObjectPrefix" value="LR_C_">
</journal>
</cluster>
</repository>
That problem exists with Jacrabbit and Oracle or where is the problem?
I tried to patch jackrabbit following some post, but without success, [url=https://issues.apache.org/jira/browse/JCR-1907?
page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel]JIRA-1907
I tested with the parameters jndi:
<param name="driver" value="javax.naming.InitialContext">
<param name="url" value="java:comp/env/jdbc/LiferayPool">
Throwing Error is: "jdbc not bound"
Has anyone encountered this?
Thanks and greetings to all!
Ricardo Martínez, geändert vor 12 Jahren.
RE: Problem by setting jndi jackrabbit with oracle (FileSystem) (Antwort)
New Member Beiträge: 6 Beitrittsdatum: 27.05.10 Neueste Beiträge
Hi all,
For your information.
I upgraded to version 2.2.9 of jackrabbit following the steps in this post:
How to upgrade Jackrabbit and it works correctly in the repository database through oracle 11g2 Jackrabbit.
Configuring the repository.xml JNDI (FileSystem / Worskpace / Versioning / Cluster)
For your information.
I upgraded to version 2.2.9 of jackrabbit following the steps in this post:
How to upgrade Jackrabbit and it works correctly in the repository database through oracle 11g2 Jackrabbit.
Configuring the repository.xml JNDI (FileSystem / Worskpace / Versioning / Cluster)
<param name="driver" value="javax.naming.InitialContext">
<param name="url" value="java:jdbc/LiferayPool">