Since upgrading from JBoss 2.0 FINAL to 2.2.1 my system has developed a bug
- an exception is thrown from a call to ResultSet.last(). The exception is
thrown because the ResultSet is of type TYPE_FORWARD_ONLY.
>From searching the mail-archive it appears that this is down to a bug in the
minerva XADataSourceImpl which always returns a ResultSet of type
TYPE_FORWARD_ONLY.
My system configuration is JBoss 2.2.1 with embedded Tomcat 3.2.1 on Solaris
2.6 with Oracle 8.1.7.
In an attempt to fix my bug I have tried using Oracle's XADataSource classes
(classes12.zip). I have tried the following datasource configurations:
<mbean code="org.jboss.jdbc.RawXADataSourceLoader"
name="DefaultDomain:service=XADataSource,name=OracleDS">
<attribute name="PoolName">OracleDS</attribute>
<attribute
name="DataSourceClass">oracle.jdbc.xa.client.OracleXADataSource</attribute>
<attribute
name="Properties">URL=jdbc:oracle:thin:user/password@host:1521:sid</attribut
e>
</mbean>
and
<mbean code="org.jboss.jdbc.XADataSourceLoader"
name="DefaultDomain:service=XADataSource,name=OracleDS">
<attribute name="PoolName">OracleDS</attribute>
<attribute
name="DataSourceClass">oracle.jdbc.xa.client.OracleXADataSource</attribute>
<attribute name="URL">jdbc:oracle:thin:@host:1521:sid</attribute>
<attribute name="JDBCUser">user</attribute>
<attribute name="Password">password</attribute>
</mbean>
Whilst both of these services initialise without error - the behaviour of
the running application is unreliable in either configuration, (transaction
timeouts etc.).
So where do I go from here ?
My next step is to go back to the minerva XADataSourceImpl and re-work the
code to remove the need for scrollable ResultSets.
Any better suggestions ?
Richard.
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
