jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "PREVOSTO, Laurent" <laurent.prevo...@sfr.com>
Subject JackRabbit DS should be XA or unmanaged ?
Date Thu, 12 Aug 2010 23:04:11 GMT
i am still struggling with my JCR-2679 problem :

Basically, sometimes, th BundlePM won't be able to reconnect to the database and as it is
in a synchronized method, the whole webapp gets stuck :-(

After browsing through docs and forums, i am really confused by the desired configuration
of the JackRabbit DS :

it looks like the BundlePM manages its own JDBC connection, hence the JackRabbit DS should
not be managed by JBOSS.

Today, our JackRabbit DS looks like :

                <track-connection-by-tx />
                <xa-datasource-property name="URL">jdbc:oracle:thin:@fubar</xa-datasource-property>
                <xa-datasource-property name="User">xxxx</xa-datasource-property>
                <xa-datasource-property name="Password">yyyyy</xa-datasource-property>
                        Uses the pingDatabase method to check a connection is still valid
                        before handing it out from the pool
                <!-- Checks the Oracle error codes and messages for fatal errors -->
                        Oracles XA datasource cannot reuse a connection outside a transaction
                        once enlisted in a global transaction and vice-versa
                <no-tx-separate-pools />
                        corresponding type-mapping in the standardjbosscmp-jdbc.xml
                <!--<check-valid-connection-sql>SELECT user FROM dual</check-valid-connection-sql>-->

But some people tend to say that the JackRabbit DS should be unnmanaged (<no-tx-datasource/>)
as in JCR-1349

What is the good way of configuring the JackRabbit DS ?



View raw message