[
https://issues.jboss.org/browse/TEIID-2302?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-2302:
---------------------------------------
The docs do show the use of the xa-datasource-property -
https://docs.jboss.org/author/display/AS71/Admin+Guide - as a way to specify properties
that are set on the DataSource instance. It also shows the security element being used as
well.
TEIID10006 is a very low level error probably occurring when the login traffic is being
encrypted/decrypted - however I can't see that it would make a difference to us
whether the security or xa-datasource-property mechanism were used. Perhaps the security
mechanism is altering the thread context classloader to one that has no knowledge of the
client classes. If that's the case, we could treat that as an AS issue and/or could
address by giving our Cryptor a classloader to use (which should just be the classloader
that loaded the class).
Issues setting up Teiid as an XA datasource in AS 7
---------------------------------------------------
Key: TEIID-2302
URL:
https://issues.jboss.org/browse/TEIID-2302
Project: Teiid
Issue Type: Bug
Components: Build/Kits
Affects Versions: 8.2
Reporter: Van Halbert
Assignee: Van Halbert
Priority: Minor
Ran across 2 issues when trying to setup Teiid as a XA data source based on the
teiid-xa-ds.zml in the jboss kit: docs/teiid/datasources/teiid/teiid-xa-ds.xml
1 - ClassNotFound for the org.hibernate.dialect.Dialect, so added:
<module name="org.hibernate"/>
to the teiid/client/main/module.xml
2 - seeing this error: TEIID10006 Decryption failed: java.lang.ClassNotFoundException
org.teiid.client.util.ExceptionHolder from [Module "org.jboss.jts:main" but
that was resolved after I changed security from:
<security>
<user-name>user</user-name>
<password>user</password>
</security>
to:
<xa-datasource-property name="User">
user
</xa-datasource-property>
<xa-datasource-property name="Password">
user
</xa-datasource-property>
--
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