jboss.jca
* service=CachedConnectionManager
* service=LocalTxPool,name=DefaultDS
* service=XATxCM,name=DocsDS
* service=XATxDS,name=DocsDS
* service=LocalTxPool,name=DocsDS
* service=RARDeployment,name=JMS Adapter
* service=DataSourceDeployer
* service=LocalTxDS,name=DefaultDS
* service=XaTxPool,name=jmsra
* service=XaTxCM,name=jmsra
* service=RARDeployer
* service=LocalTxCM,name=DefaultDS
* service=RARDeployment,name=JBoss LocalTransaction JDBC Wrapper
* service=RARDeployment,name=JBoss JDBC XATransaction ResourceAdapter
* service=XaTxDS,name=jmsra
Thanks again for your help,
David
PS: This is jboss-3.2.0beta2_tomcat-4.1.12. I can't use beta3 yet since there is not tomcat bundle for it on SourceForge.
--
Igor Fedorenko escribi�::
David Ward wrote:The oracle-xa-service.xml file seems like the old 3.0 style...1) Do we need it? Can we just use oracle-xa-ds.xml?You can use oracle-xa-ds.xml.
2) If I just use oracle-xa-ds.xml, do I still need to use the "Pad" true for the XidFactory in transaction-service.xml?
Yes, you need to set Pad=true.3) Is there any other file I have to touch?No.(JBoss 3.2b2+, JDK 1.4.1_01) Thanx, David
2003-01-09 10:54:28,320 ERROR [org.jboss.deployment.scanner.URLDeploymentScanner] MBeanException: Exception in MBean operation 'checkIncompleteDeployments()' Cause: Incomplete Deployment listing: Packages waiting for a deployer: <none> Incompletely deployed packages: <none> MBeans waiting for classes: <none> MBeans waiting for other MBeans: [ObjectName: jboss.jca:service=XATxCM,name=DocsDS state: CONFIGURED I Depend On: jboss.jca:service=XATxDS,name=DocsDS jboss.jca:service=LocalTxPool,name=DocsDS jboss.jca:service=CachedConnectionManager jboss.security:service=JaasSecurityManager jboss.jca:service=RARDeployer Depends On Me: , ObjectName: jboss.jca:service=XATxDS,name=DocsDS state: CONFIGURED I Depend On: jboss.jca:service=RARDeployment,name=Minerva JDBC XATransaction ResourceAdapter Depends On Me: jboss.jca:service=XATxCM,name=DocsDS ]
<?xml version="1.0" encoding="UTF-8"?>
<!-- ===================================================================== -->
<!-- -->
<!-- JBoss Server Configuration -->
<!-- -->
<!-- ===================================================================== -->
<!-- $Id: oracle-xa-ds.xml,v 1.1.2.1 2002/10/29 21:24:14 starksm Exp $ -->
<!-- ==================================================================== -->
<!-- ConnectionManager setup for xa oracle dbs -->
<!-- Thanks to igor fedorenko <[EMAIL PROTECTED]> -->
<!-- Build jmx-api (build/build.sh all) and view for config documentation -->
<!-- YOU MUST CHANGE THE XidFactoryMBean config to this: -->
<!--
Note: I set Pad=true in transaction-service.xml
<mbean code="org.jboss.tm.XidFactory"
name="jboss:service=XidFactory">
<attribute name="Pad">true</attribute>
</mbean>
-->
<!-- ==================================================================== -->
<datasources>
<xa-datasource>
<jndi-name>DocsDS</jndi-name>
<!-- The following optionally turns on the TrackConnectionByTx property
of XATxConnectionManager. This property creates a 1 to 1 mapping of
JDBC connections to transactions and prevents a connection from
participating in more than one transaction at the same time. Setting this
to true seems to fix quite a few Oracle XA bugs. -->
<track-connection-by-tx>true</track-connection-by-tx>
<managedconnectionfactory-class>org.jboss.resource.adapter.jdbc.xa.oracle.XAOracleManagedConnectionFactory</managedconnectionfactory-class>
<xa-datasource-property name="URL">jdbc:oracle:thin:@foo:1521:bar</xa-datasource-property>
<xa-datasource-property name="User">scott</xa-datasource-property>
<xa-datasource-property name="Password">tiger</xa-datasource-property>
</xa-datasource>
</datasources>
