I added a comment in that JIRA:
I think (as I mention in another comment in there) that this is related to https://issues.jboss.org/browse/AS7-5336
As an aside, Oracle doesn't appear to support 10g's original release (10.0) anymore - and 10.1 extended support ended this past January. You can see this in the pdf file located at the bottom of http://www.oracle.com/us/support/lifetime-support/index.html - the link "Lifetime Support Policy: Oracle Technology Products". So it appears they don't even support 10.0 and probably haven't for a while. 10.0 isn't even on their support matrix chart; only 10.1 and 10.2 (in the 10g family) is listed.
This is relevent because, as per:
"The SetBigStringTryClob connection property of Oracle Database 10g Release 1 (10.1) is no longer used or needed"
so this means all their supported 10g releases don't need it.
sorry for the spam, but it was brought to my attention that I might be misinterpreting that quote from the Oracle docs "The SetBigStringTryClob connection property of Oracle Database 10g Release 1 (10.1) is no longer used or needed". I read that as "Oracle 10.1 and up no longer needs it" but I think it really is saying "that property that was in 10.1 (an apparently used) is no longer needed or used in later versions".
So I may be wrong that it isn't used in 10.1.
Yeah, with Oracle Database 11g release 2 (11.2), the property isn't needed anymore. With previous versions back to Oracle Database 10g Release 1 (10.1), the problem still persists.
I'm having a similiar issue using xa-datasoure-property to set ConnectionProperties on an Oracle connection. Specifically, <xa-datasource-property name="ConnectionProperties">oracle.jdbc.ReadTimeout=30000</xa-datasource-property>
I don't get a fatal error but, the property seems to be ignored and I never see the OracleDataSource.setConnectionProperties() method get called.