Bugs item #542371, was opened at 2002-04-11 00:17
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=376685&aid=542371&group_id=22866

Category: JBossServer
Group: v2.4 (stable)
Status: Open
>Resolution: Accepted
Priority: 5
Submitted By: Chris Harris (charris)
>Assigned to: Scott M Stark (starksm)
Summary: 2.4.5 no XA JDBC w/ XADataSourceLoader

Initial Comment:
Testing an upgrade from 2.4.3 to 2.4.5RC1 we find we 
are unable to use our existing configuration for our 
database connections.

<mbean code="org.jboss.jdbc.XADataSourceLoader" 
name="DefaultDomain:service=XADataSource,name=DefaultDS
">
    <attribute name="PoolName">DefaultDS</attribute>
    <attribute 
name="DataSourceClass">com.inet.tds.XDataSource</attrib
ute>
    <attribute 
name="DataSourceClass">org.jboss.pool.jdbc.xa.wrapper.X
ADataSourceImpl</attribute>
    <attribute 
name="URL">jdbc:inetdae7:127.0.0.1</attribute>
    <attribute name="JDBCUser">chrisharris</attribute>
    <attribute name="Password">chrisharris</attribute>
        <attribute 
name="LoggingEnabled">false</attribute>
        <attribute 
name="Properties">host=127.0.0.1;database=chrisharris</
attribute>
        <attribute 
name="GCMinIdleTime">1200000</attribute>
        <attribute name="MaxSize">20</attribute>
        <attribute name="GCEnabled">false</attribute>
        <attribute 
name="InvalidateOnError">false</attribute>
        <attribute 
name="TimestampUsed">false</attribute>
        <attribute name="Blocking">true</attribute>
        <attribute name="GCInterval">120000</attribute>
        <attribute 
name="IdleTimeout">1800000</attribute>
        <attribute 
name="IdleTimeoutEnabled">false</attribute>
        <attribute 
name="MaxIdleTimeoutPercent">1.0</attribute>
        <attribute name="MinSize">0</attribute>
  </mbean>

This previously worked very well, but now triggers 
ClassCastExceptions in XAConnectionFactory because it 
is assumed that all JDBC Connections are in fact 
jboss' own XAConnectionImpl. In other words, using 
XADataSourceLoader is now *only* possible if you have 
a non-XA driver and the loader uses its own datasource 
implementation (XADataSourceImpl)!

I will try and use a RAR instead from the 3.0 
codebase. However this is a big, incompatible, change 
and I don't know if the JCA support is there in 2.4.5.

----------------------------------------------------------------------

Comment By: Chris Harris (charris)
Date: 2002-04-11 01:33

Message:
Logged In: YES 
user_id=8915

Stack trace follows:

java.lang.ClassCastException: com.inet.tds.k
        at 
org.jboss.pool.jdbc.xa.XAConnectionFactory.checkValidObject
(XAConnectionFactory.java:391)

        at org.jboss.pool.ObjectPool.getObject
(ObjectPool.java:631)
        at 
org.jboss.pool.jdbc.xa.XAPoolDataSource.getConnection
(XAPoolDataSource.java:215)
        at 
com.lombardrisk.jbossinfra.audit.AuditTrailLog.getStoredCoun
terValue(AuditTrailLog.java:1
48)
        at 
com.lombardrisk.jbossinfra.audit.AuditTrailLog.startService
(AuditTrailLog.java:116)
        at org.jboss.util.ServiceMBeanSupport.start
(ServiceMBeanSupport.java:103)
        at java.lang.reflect.Method.invoke(Native Method)
        at com.sun.management.jmx.MBeanServerImpl.invoke
(MBeanServerImpl.java:1628)
        at com.sun.management.jmx.MBeanServerImpl.invoke
(MBeanServerImpl.java:1523)
        at 
org.jboss.configuration.ConfigurationService$ServiceProxy.in
voke(ConfigurationService.jav
a:967)
        at $Proxy0.start(Unknown Source)
        at org.jboss.util.ServiceControl.start
(ServiceControl.java:79)
        at java.lang.reflect.Method.invoke(Native Method)
        at com.sun.management.jmx.MBeanServerImpl.invoke
(MBeanServerImpl.java:1628)
        at com.sun.management.jmx.MBeanServerImpl.invoke
(MBeanServerImpl.java:1523)
        at org.jboss.Main.<init>(Main.java:208)
        at org.jboss.Main$1.run(Main.java:110)
        at java.security.AccessController.doPrivileged
(Native Method)
        at org.jboss.Main.main(Main.java:106)

It's down to the XAConnectionFactory.checkValidObject being 
*much* stricter about what it will accept now - it won't 
let any implementation of javax.sql.XAConnection through 
(i.e. a vendor impl) but insists on using JBoss' own semi-
XA wrapper implementation class.

----------------------------------------------------------------------

Comment By: Scott M Stark (starksm)
Date: 2002-04-11 00:28

Message:
Logged In: YES 
user_id=175228

Show the stack trace.

----------------------------------------------------------------------

You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=376685&aid=542371&group_id=22866

_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to