Colin
David Jencks wrote:
Please indicate the exact jboss version you are using and exactly where you
got the oracle-xa-service.xml from.
I recently changed the xa wrapper in 3.2 and may not have updated all the
references to the old wrapper. A mismatch such as this would explain what
you are experiencing.
thanks
david jencks
On 2002.11.20 18:30:15 -0500 Colin Sampaleanu wrote:
I have encountered a really perplexing issue with trying to get an oracle xa datasource (using either oracle-xa-ds.xml or oracle-xa-service.xml). Basically, it never deploys fully, with the following dependency issues:
---
17:10:37,471 ERROR [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=XAOracleDS state: CONFIGURED
I Depend On: jboss.jca:service=RARDeployer
jboss.jca:service=XATxDS,name=XAOracleDS
jboss.jca:service=XATxPool,name=XAOracleDS
jboss.jca:service=CachedConnectionManager
jboss.security:service=JaasSecurityManager
Depends On Me: , ObjectName: jboss.jca:service=XATxDS,name=XAOracleDS state: CONFIGURED
I Depend On: jboss.jca:service=RARDeployment,name=Minerva JDBC XATransactionResourceAdapter
Depends On Me: jboss.jca:service=XATxCM,name=XAOracleDS
---
Now what is really weird is that there are no other errors in the log at all. It is as if the "jboss.jca:service=RARDeployment,name=Minerva JDBC XATransaction ResourceAdapter" mbean is simply hanging or something. It doesn't give any errors. This is basically the stock oracle-xa-ds.xml, with the URL set properly (to 'URL=jdbc:oracle:thin:@tiradev:1521:tira' in this case), the proper user and pass, and that's about it. Using oracle-service.xml, the result is the same (as it should be). Here is a copy of the relevant portion of oracle-xa-ds.xml:
-----
<datasources>
<xa-datasource>
<jndi-name>DefaultDS</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>
<xa-datasource-class>oracle.jdbc.xa.client.OracleXADataSource</xa-datasource-class>
<xa-datasource-property name="URL">jdbc:oracle:thin:@tiradev:1521:tira</xa-datasource-property>
<!-- Not needed?
<xa-datasource-property name="DatabaseName">mydatabase</xa-datasource-property>
-->
<user-name>whatever</user-name>
<password>whatever2</password>
</xa-datasource>
</datasources>
-----
The same database can be accessed through the non xa variant, although I am having some deadlocks, which was why I wanted to try xa in the first place. I have btw renamed the existing HSQL datasource to another JNDI name so it doesn't conflict. I would also try to log JDBC calls, if I could figure out how to make JBoss issue the appropriate call on DriverManager (the only way I know how to turn on JDBC logging).
Regards,
Colin
------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
