WebSphere® Adapter for JDBC version 6.0.2 has been updated.
WebSphere Adapter for JDBC fix pack version 184.108.40.206
Internal tracking number 90872/JR27717: Adapter for JDBC generates a ConnectionObjectClosed error with data sources after the database goes down.
Symptom: When the adapter is configured to use a predefined data source and the database system goes down while the adapter is processing the requests, the adapter fails to recover the connection after the database system is restarted.
Resolution: The adapter now generates a connection error event for the stale managed connection, which is then removed from the managed connection pool. Subsequent requests are processed successfully.
Internal tracking number 90821 : Event logging fails when an adapter from version 6.0.2 is started using WebSphere Enterprise Service Bus, version 6.1 or WebSphere Process Server, version 6.1.
Symptom: The adapter generated an org.eclipse.hyades.logging.events.cbe.MissingPropertyException error whenever event logging was enabled.
Resolution: The event logging service in WebSphere Enterprise Service Bus and WebSphere Process Server was modified in version 6.1 and now requires additional input parameters. The WebSphere Adapters code has been updated to provide these parameters so that events are logged successfully.
Internal tracking number 90722/JR27593: Time zone differences between the WebSphere Application Server logs and adapter log files
Symptom: The time zone format in the log files generated by the adapter does not match the time zone format in the WebSphere Application Server log files.
Resolution: The time zone format has been modified in the adapter to match the time zone format in the WebSphere Application Server log files. The adapter will log the messages in local time zone dateFormat=yyyy/MM/dd HH:mm:ss:SSS zzz.
Internal tracking number 70276 : UnknownSQLType error with int type in DB2®
Symptom: During inbound processing, the adapter generates an UnknownSQLType error message while processing an event for a business object with attributes of type int.
Resolution: The adapter correctly processes business objects with int datatypes.
Internal tracking number 89830 : UnknownSQLType: -99999
Symptom: During outbound processing, the adapter generates an UnknownSQLType error message while processing a business object containing attributes with primitive datatypes.
Resolution: The adapter correctly processes business objects with primitive datatypes.
Internal tracking number 90339 : Connection leakage during rollback of a transaction for event delivery Symptom: After delivering the event to the endpoint, the adapter updates the status of the event in the event table. When the event has been successfully delivered, commit is called and the event is marked as delivered. However, if the adapter fails to update the event status, it generates an XAException error with error code XA_RETRY. In this case, transaction manager keeps retrying the commit on all participants in the global transaction and every retry results in a new connection being created in the connection pool. Eventually, the connection pool will be exhausted, resulting in connection timeout issues.
Now, if the event delivery fails, rollback is called and the event is marked as new and ready to poll again. If any of these operations fails, the transaction is rolled back, which might result in a connection leak. The operations to update the event status and mark the event as new are likely to fail due to data related issues or to an external application modifying the data in the event table. Also, this problem occurs only when Adapter for JDBC is configured to use data source JNDI.
Internal tracking number 90074: ExhaustedResultSet error
Symptom: After delivering the event to the endpoint, the adapter updates the status of the event in the event table. However, if the event has been externally deleted from the event table, the adapter generates an ExhaustedResultSet error.
Resolution: The adapter no longer generates the error.
Internal tracking number 89285 : Filter future events feature is not working for the adapter
Symptom: When the FilterFutureEvents property is set to true and an event is polled, the following resource exception is generated, "javax.resource.ResourceException: Event timestamp is null."
Resolution: The resource exception is no longer generated when the filter future events feature is used.
Internal tracking number 89548/JR27115: Adapter for JDBC trims space from object_key
Symptom: During inbound event delivery, the adapter trims space from object_key before retrieving the object based on the object key specified in the event table.
Resolution: The adapter provides an additional Boolean property (performTrimOnObjectKeyValue) on the ActivationSpec. The value set on this property determines whether the adapter trims the value set on object_key or not. The default value for this property is true, which means that by default, the adapter will trim the value set on the object_key. If you do not want the adapter to trim the spaces in object_key, set this property to false.
Internal tracking number 89357 : The adapter does not terminate normally
Symptom: The adapter does not roll back failed global transactions during inbound event delivery, so the WebSphere Application Server transaction manager keeps retrying the transactions.
Resolution: The adapter rolls back the transactions in the case of a failure.
Internal tracking number 89356 : Database Lock after transaction rollback
Symptom: The adapter does not roll back failed global transactions during inbound event delivery. You might see the following messages in the trace file:
1. Limit for number of MessageEndpoint proxies created reached.
2. TimeoutManager I WTRN0006W: Transaction "TRANSACTION_ID" has timed out after 200 seconds. 3. SQLException: distributed transaction waiting for lock This message is specific for the Oracle database; however, you will likely see a similar message for other databases as well.
Resolution: The adapter rolls back the transactions in the case of failure.
Enhancements in version 220.127.116.11
Internal tracking number 72741: Enterprise service discovery wizard is enabled for all manual application-specific information editing.
Enterprise service discovery wizard can build a hierarchy of both multiple and single cardinality child business objects, including KeepRelationship, Ownership, and Required application-specific information by getting user input and setting foreign keys appropriately in the parent and child business objects.
Internal tracking number 72810: A new property, DriverConnectionProperties, has been added.
The new property has been added to the managed connection factory and activation specification.
Internal tracking number 60808: Prepared statement caching is supported.
The adapter now supports prepared statement caching. This feature is available only if a data source is used to connect to the database.
Internal tracking number 72815: Support is needed for generating appropriate application-specific information for globalized data types.
Support for the following globalized data types is now provided: NCHAR, NVARCHAR, NTEXT, TEXT, RAW, MONEY, and SMALLMONEY.
Internal tracking number 72805: Support for wrapper business objects has been added.
Support is provided for the construction of wrapper business objects in the Enterprise Metadata Discovery.
Internal tracking number 68834: The enterprise service discovery wizard displays stored procedure (SP) names as SPName (PkgName).
Stored procedures are now displayed in the enterprise service discovery wizard as SPName (PackageName), sorted by SPName. For example, if package A includes one stored procedure called DSP, and package B includes another stored procedure called CSP, the enterprise service discovery wizard displays these two stored procedures in the following order: CSP(B) DSP(A).
Internal tracking number 86355: Equivalent support of the WebSphere Business Integration Adapter application-specific information, UNVL, is needed in the JCA adapter. UNVL equivalent support is now provided.
Fixes in version 18.104.22.168:
Internal tracking number 87658/APAR JR26244: Trigger usage with MS SQL Server 2000 returns the wrong User Identity (UID).
With MS SQL Server 2000, when a row is inserted into a table, for instance "customer," a trigger is executed and a row is added to the event table. Both tables use the Identity column as the primary key. For further processing, the UID of the inserted "customer" row should be retrieved, but the adapter retrieves the UID of the row inserted into the event table instead. This has been fixed and the adapter returns the correct UID.
Internal tracking number 87349/APAR JR26243: The Update operation on a business object with n-cardinality children creates the last child business object only if it is not there already. This has been fixed and the adapter appropriately processes the n-cardinality children.
Internal tracking number 88947/ APAR JR26628: The adapter retrieves incorrect data for child objects when a parent business object contains two single cardinality children with foreign keys referring to the same attribute. This has been fixed, and the adapter correctly retrieves the data for single cardinality children.
Internal tracking number 89008: With some requests, the adapter generates the SQLException "maximum open cursors exceeded" after retrieving data from an Oracle database. This problem has been fixed and the adapter is closing the open resultset and statement objects.
Internal tracking number 69773: The adapter generates a NullPointerException exception when using the Custom delete query for an inbound operation. This has been fixed and the adapter appropriately processes the Custom delete query.
Fixes in version 22.214.171.124:
Internal tracking number 69043: Unable to connect to a database using XADataSourceName and XADatabaseName properties configured in the managed connection factory. This has been fixed and the adapter can connect to the database when configured with these properties.
Internal tracking number 87193: The execute operation on the stored procedure fails when the stored procedure has IN OUT (IO) parameters. This has been fixed for data types other than CLOB and BLOB. For details about CLOB and BLOB support, refer to the JDBC adapter technotes.
Internal tracking number 87159: The adapter generates a ClassCastException exception for binary types within a stored procedure. This has been fixed and binary data types are handled correctly.
Internal tracking number 87216: When returning BLOB data, the adapter returns the length of the BLOB data instead of the content of the BLOB data. This has been fixed and adapter now returns the content of BLOB data.
This fix pack should be installed on Version 6.0.2 of WebSphere Adapter for JDBC.
Note: If you are using WebSphere Integration Developer, upgrade the adapter using WebSphere Integration Developer 602 (with the latest interim fix).
Install the fix by following these instructions:
1. Download the file for your operating system.
2. Unzip the archive to a temporary location.
3. Run the appropriate setup file for the operating system and install it to the same folder that contains the RAR file from the 6.0.2 version of the adapter.
To deploy adapters on AIX®, HP-UX, and Solaris platforms, generate new EAR files from the updated RAR file after applying the fix pack, using the enterprise service discovery wizard available with WebSphere Integration Developer on Windows® or Linux® platforms. The new EAR file can then be deployed to WebSphere Process Server on the respective platform.
For more setup information, follow the detailed instructions in the Adapter for JDBC ReadMe.htm file within the fix pack.
|Download||RELEASE DATE||LANGUAGE||SIZE(Bytes)||Download Options|
|JDBC FP 126.96.36.199 for Windows||12/15/2007||English||104426339||FTP|
|JDBC FP 188.8.131.52 for Linux||12/15/2007||English||109159170||FTP|