[jboss-jira] [JBoss JIRA] (AS7-4673) Failure to set "SetBigStringTryClob=true" ConnectionProperties in xa-datasource-property
Roger S (JIRA)
jira-events at lists.jboss.org
Mon Dec 10 21:11:17 EST 2012
[ https://issues.jboss.org/browse/AS7-4673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12740510#comment-12740510 ]
Roger S commented on AS7-4673:
------------------------------
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.
> Failure to set "SetBigStringTryClob=true" ConnectionProperties in xa-datasource-property
> ----------------------------------------------------------------------------------------
>
> Key: AS7-4673
> URL: https://issues.jboss.org/browse/AS7-4673
> Project: Application Server 7
> Issue Type: Bug
> Components: JCA
> Affects Versions: 7.1.1.Final
> Environment: Red Hat Enterprise Linux Server release 5.7, JDK 7, Oracle 10g
> Reporter: Roger S
> Assignee: Stefano Maestri
> Labels: rhq
>
> I found that when the following is set in the standalone.xml of JBoss-7.1.1.Final, it will have a fatal error:
> <xa-datasource....>
> ....
> <xa-datasource-property name="ConnectionProperties">SetBigStringTryClob=true</xa-datasource-property>
> ....
> </xa-datasource>
> The error is:
>
> Caused by: javax.resource.ResourceException: No property editor found for type: class java.util.Properties
> at org.jboss.jca.adapters.jdbc.xa.XAManagedConnectionFactory.getXADataSource(XAManagedConnectionFactory.java:601)
> at org.jboss.jca.adapters.jdbc.xa.XAManagedConnectionFactory.getXAManagedConnection(XAManagedConnectionFactory.java:430)
>
> When I don't define the SetBigStringTryClob setting, all is fine. However, the SetBigStringTryClob is really important for the application to work correctly. Hope there's at least a workaround.
> This worked without problems in JBoss 4.2.3.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list