The following bugs have been fixed in XMLink 2.2.
|
Bug Number |
Description |
|
36650 |
ManagedConnectionFactoryImpl.getUserName() fails to return the value of the UserName property set by ManagedConnectionFactoryImpl.setUserName(). |
|
36652 |
XMLink does not send the CONNECTION_ERROR_OCCURRED event notification to the ConnectionEventListener when a service call fails with the TPED_TERM error detail code from Tuxedo. Due to this, WebSphere then leaves the bad connection in the pool to be used again. |
|
36656 |
FML and FML32 buffers often cannot be used due to corruption of the environment variables FIELDTBLS, FIELDTBLS32, FLDTBLDIR, and FLDTBLDIR32. |
|
36657 |
Performance degradation due to calls back into Java classes from JNI. |
|
36658 |
No exception is thrown for ManagedConnectionImpl.getXAResource. The Connector Architecture Specification says that if the resource adapter does not support XA transactions javax.resource.NotSupportedException should be thrown. |
|
36659 |
<transaction-support> tag in ra.xml file inside tconn.rar should should contain the value, NoTransaction, for Tuxedo 6.5. It currently uses LocalTransaction, which is correct for Tuxedo 7.1. |
|
36661 |
CONNECTION_ERROR_OCCURRED notification not sent on Tux7 service call failure, due to lost connection. This limits failover capabilities when using XMLink with Tuxedo 7.1. |
|
36665 |
JVM crashes when using FML, if a field is missing in the FML field table. |
|
36667 |
At most, 50 simultaneous service calls can be made using XMLink with Tuxedo 6.5. |
|
36676 |
Error codes are 0 and error strings are empty in TuxedoException that gets thrown when tpinit() fails. |
|
36678 |
Documentation error: tconn.dll only lists WebSphere 3.5 |
|
36686 |
XMLink doesn’t save connection pooling info. |
|
36695 |
Records are not serializable. |
|
36742 |
Documentation error: change ltx.end() to ltx.commit(). |
|
36756 |
javax.resource.cci.ConnectionFactory.getConnection() core dumps on AIX4.3.3. |