[ 
https://issues.apache.org/jira/browse/JCR-3166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13259602#comment-13259602
 ] 

nick commented on JCR-3166:
---------------------------

Its way too old anyway i found a work around for this long back i forgot to 
update here... 
This issue is not related to jackrabbit-ocm but with springmodule-jcr.

If you configure JcrSessionFactory like the below it will work in JBoss AS 7
{code:xml}
<bean id="sessionHolderProviderManager" 
class="org.springmodules.jcr.support.ServiceSessionHolderProviderManager"/>

        <bean id="jcrSessionFactory" 
class="org.springmodules.jcr.JcrSessionFactory">
                <property name="repository" ref="repository"/>
                <property name="workspaceName" value="DOCMGMT" />
                <property name="credentials">
                        <bean class="javax.jcr.SimpleCredentials">
                                <constructor-arg index="0" value="bogus"/>
                                <constructor-arg index="1">
                                        <bean factory-bean="password" 
factory-method="toCharArray"/>
                                </constructor-arg>
                        </bean>
                </property>
                <property name="sessionHolderProviderManager" 
ref="sessionHolderProviderManager"/>
                <property name="forceNamespacesRegistration" 
value="false"></property>
                <property name="keepNewNamespaces" value="true"></property>
                <property name="skipExistingNamespaces" value="true"></property>
                <property name="namespaces">
                        <props>
                                <prop 
key="ocm">http://jackrabbit.apache.org/ocm</prop>
            </props>
                </property>
        </bean>
{code}
                
> jackrabbit is not working in JBoss AS7.1.0
> ------------------------------------------
>
>                 Key: JCR-3166
>                 URL: https://issues.apache.org/jira/browse/JCR-3166
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: jackrabbit-core
>    Affects Versions: 2.3.4
>         Environment: JBoss AS 7.1.0 + Jackrabbit OCM + Spring JCR Module + 
> Jackrabbit-JCA 2.3.4 on Windows
>            Reporter: nick
>
> Jackrabbit-jca 2.3.4.rar deployment was successful but its not creating 
> jackrabbit specific tables (using postgresql). The intention behind filing it 
> as a bug because, with Jackrabbit-jca-1.6.5.rar deployment is successful and 
> its creating relevant tables but its giving a different exception while 
> trying to add some document to the repository as follows.
> Illegal logical session called.
> With jackrabbit-jca-2.3.4 i'm getting the following error while i try to add 
> a document to the repository.
>     Failed to create session: Unable to access a repository with the 
> following settings: org.apache.jackrabbit.repository.conf: 
> C:\Server\jboss-as-7.1.0.Alpha2-SNAPSHOT\standalone\configuration\jackrabbit\repository.xml
>  org.apache.jackrabbit.repository.home: 
> C:\Server\jboss-as-7.1.0.Alpha2-SNAPSHOT\standalone\data\jackrabbit The 
> following RepositoryFactory classes were consulted: Perhaps the repository 
> you are trying to access is not available at the moment.
>     IJ000658: Unexpected throwable while trying to create a connection: null
>     javax.resource.ResourceException: IJ000658: Unexpected throwable while 
> trying to create a connection: null
> 17:36:26,363 WARN  
> [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] 
> (http-127.0.0.1-127.0.0.1-8080-1) IJ000604: Throwable while attempting to get 
> a new connection: null: javax.resource.ResourceException: Failed to create 
> session: Unable to access a repository with the following settings:
>     org.apache.jackrabbit.repository.conf: 
> C:\Server\jboss-as-7.1.0.Alpha2-SNAPSHOT\standalone\configuration\jackrabbit\repository.xml
>     org.apache.jackrabbit.repository.home: 
> C:\Server\jboss-as-7.1.0.Alpha2-SNAPSHOT\standalone\data\jackrabbit
> The following RepositoryFactory classes were consulted:
> Perhaps the repository you are trying to access is not available at the 
> moment.
>     at 
> org.apache.jackrabbit.jca.JCAManagedConnection.openSession(JCAManagedConnection.java:107)
>     at 
> org.apache.jackrabbit.jca.JCAManagedConnection.<init>(JCAManagedConnection.java:85)
>     at 
> org.apache.jackrabbit.jca.JCAManagedConnectionFactory.createManagedConnection(JCAManagedConnectionFactory.java:163)
>     at 
> org.apache.jackrabbit.jca.JCAManagedConnectionFactory.createManagedConnection(JCAManagedConnectionFactory.java:155)
>     at 
> org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool.createConnectionEventListener(SemaphoreArrayListManagedConnectionPool.java:736)
>     at 
> org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool.getConnection(SemaphoreArrayListManagedConnectionPool.java:341)
>     at 
> org.jboss.jca.core.connectionmanager.pool.AbstractPool.getTransactionNewConnection(AbstractPool.java:492)
>     at 
> org.jboss.jca.core.connectionmanager.pool.AbstractPool.getConnection(AbstractPool.java:373)
>     at 
> org.jboss.jca.core.connectionmanager.AbstractConnectionManager.getManagedConnection(AbstractConnectionManager.java:332)
>     at 
> org.jboss.jca.core.connectionmanager.tx.TxConnectionManagerImpl.getManagedConnection(TxConnectionManagerImpl.java:367)
>     at 
> org.jboss.jca.core.connectionmanager.AbstractConnectionManager.allocateConnection(AbstractConnectionManager.java:448)
>     at 
> org.apache.jackrabbit.jca.JCARepositoryHandle.login(JCARepositoryHandle.java:73)
> I have checked with all jackrabbit 2 versions but getting same error.
> I have filed the same in JBoss and Spring Community as well.
> If you feel its not a bug then please provide a solid example of integrating 
> jacrabbit-jca with JBoss AS 7. I have done the integration with Jboss just 
> like the Jackrabbit mediawiki explained.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to