This table lists the enhancements and fixes in fix pack version 2.6.9. |
Enhancements |
1 | 90337 | | Support for HP-UX on the HP Integrity platform is needed |
Symptom:
The adapter should be supported for HP-UX on the HP Integrity platform
|
Resolution:
Support is provided
|
|
2 | 95501 | | Enhancement of the TimingStats feature |
Symptom:
The infomation in log file for TimingStats is not complete
|
Resolution:
The property BOInstanceTimingStats has been added to the business object. The BOInstanceTimingStats property has higher priority than the TimingStats property in the configuration file. When both properties are set with a valid value, the adapter uses only BOInstanceTimingStats.
|
|
3 | 95505 | | How to timeout the idle agent connections |
Symptom:
There are too many idle connections that are not being used
|
Resolution:
The property IdleTimeAndCheckInterval has been added to clear idle connections. It is a pair of integers: IdleTime and CheckInterval. The delimiter is a comma. CheckInterval specifies the cycle for checking the idle time of free connections in the JDBC connection pool. IdleTime specifies the maximum idle time. If the idle time of one free connection exceeds the value set for IdleTime, the adapter closes the connection. When the number of connections in the JDBC connection pool has reached that specified in MinimumDatabaseConnections, the adapter does not close any connections, even though some connections have been idle for a long time.
|
|
4 | 95525 | | JDBC Connector Connection Pool |
Symptom:
Redesign for JDBC Connector Connection Pool
|
Resolution:
Five new properties have been added to enable you to create connections in the JDBC connection pool.
The MaximumDatabaseConnections property specifies the maximum number of connections kept by the JDBC connection pool. It is an integer with a default value of 5.
The MinimumDatabaseConnections property specifies the minimum number of connections that should remain in the JDBC connection pool. It is an integer with a default value of 1.
The MaxDBConnectionsInBatch property specifies the maximum number of connections that can be created in batch mode at one time. It is an integer. If this property is not specified, the feature for creating batch connections is disabled.
The ThresholdOfCreatingConnectionsInBatch property sepcifies the threshold at which to start creating batch connections. It is an integer with a default value of 0.
The UsingDriverConnect property is a boolean type. If this property is true, WBI JDBC Adapter will use Driver.connect API to establish database connections. Else, DriverManager.getConnection will be used to eatablish database connections.
|
|
Fixes |
1 | 90735 | JR27571 | JDBC 2.6.6.IF1 adapter receives JDBCEventmontior exception |
Symptom: An inbound operation fails when pollForEvent begins before obtaining a valid connection. |
Resolution: The new property RetryConnCountAndInterval has been added to test a connection before fetching events. |
|
2 | 95480 | JR28117 | Adapter does not write timing messages in log |
Symptom: When using the TimingStats property, the adapter does not write the timing messages in the log file but instead writes to the trace file. |
Resolution: With the fix, the adpater will write timing messages in the log file. |
|
3 | 91600 | | Error message related to "BOInstanceTimeOut" is printed |
Symptom: Error message related to BOInstanceTimeOut is printed. |
Resolution: This problem has been fixed in enhancement 95501. |
|
4 | 89811 | JR27130 | JDBC Connector message 34043 does not provide the second parameter |
Symptom: JDBC Connector message 34043 does not provide the second parameter. |
Resolution: The second parameter has been added for message 34043. |
|
This table lists the enhancements and fixes in fix pack version 2.6.8. |
Enhancements |
1 | 89151 | | WebSphere Business Integration Adapter for JDBC business object instance level timeout |
Symptom:
Adapter for JDBC does not support business object instance level timeout. The business object instance level timeout means that different timeouts can be set to different business object instances.
|
Resolution:
The adapter now includes the BOInstanceTimeOut property (Business Object Instance TimeOut). The BOInstanceTimeOut property has higher priority than the QueryTimeOut property. When you set both BOInstanceTimeOut and QueryTimeOut with a valid value, the adapter uses BOInstanceTimeOut. Furthermore, BOInstanceTimeOut has greater coverage than QueryTimeOut. Except for the retrieve operation, BOInstanceTimeOut still covers all other operations, even the running of stored procedures.
|
|
Fixes |
1 | 89540 | JR27085 | The stored procedure can only be run for the last child business object. |
Symptom: The adapter uses only the stored procedure of the last child object to retrieve data when invoking the AfterretrieveSP stored procedure; therefore, only the last child object can have the correct data. |
Resolution: The adapter can recursively run the AfterretrieveSP stored procedure for the child business objects and will use each child business object to obtain data. |
|
2 | 69922 | | A NullPointerException exception is generated when the CloseDBConnection is set to true and PreserveUIDSeq is set to false. |
Symptom: A NullPointerException exception is generated when setting CloseDBConnection to true and PreserveUIDSeq to false. The adapter takes three minutes to shut down. |
Resolution: The problem has been fixed. |
|
This table lists the enhancements and fixes in fix pack version 2.6.7. |
Enhancements |
1 | 69348 | | Support for the Redhat Linux 4 platform |
Symptom: The adapter should be supported on the Redhat Linux 4 platform. |
Resolution: Support is provided. |
|
2 | 69137 | | Support for the Suse Linux 9 platform |
Symptom: The adapter should be supported on the Suse Linux 9 platform. |
Resolution: Support is provided. |
|
Fixes |
1 | 88523 | JR26435 | Multiple processing of events |
Symptom:
When the adapter retrieves the customer data for an inbound operation, if the connection is invalid, the adapter clears all invalid connections from the connection pool. During this process, the adapter clears the resources (Event Monitor) on the inbound connection. Therefore, the adapter cannot update the event status after finishing the previous retrieving operation, and it restarts. After restarting, the adapter continues to handle the unfinished event. So the same event is handled twice.
|
Resolution: After clearing invalid connections, the adapter initiates a new event monitor to create the necessary resources on the new polling connection. The inbound operation can then continue normally. |
|
2 | 87258 | JR25638 | A Parseexception exception occurs with Adapter for JDBC Version 2.6.5. |
Symptom:
When the attribute value is "" (CxBlank) and the data type is boolean, integer, float, double or date, the error "invalid attribute value" is generated. This problem occurs because the adapter parses the attribute value according to its data type, and "" (CxBlank) is an invalid value for these data types.
|
Resolution:
If the attribute value is "" (CxBlank) and the data type is boolean, integer, float, double or date, the adapter converts the attribute value to null, instead of generating an "invalid attribute value" error.
|
|
3 | 87160 | JR25527 | When the adapter suddenly stops polling, request processing continues |
Symptom:
After the adapter has run for a long time, the database connection might become invalid. If the connection is invalid, the outbound operation fails and the adapter clears all invalid connections. When the adapter clears the resources (Event Monitor) on the inbound connection, the polling event operation fails.
|
Resolution: After clearing the invalid connections, the adapter initiates a new event monitor to create the necessary resources on the inbound connection. The inbound operation then continues normally. |
|
This table lists the enhancements and fixes in fix pack version 2.6.6. |
Enhancements |
There are no enhancements in this fix pack. |
Fixes |
1 | 85008 | JR24342 | The CxBlank value is interpreted as null. |
Symptom: If the value of a key attribute is CxBlank and the verb is Update or Retrieve, then CxBlank is interpreted as null in the WHERE clause. |
Resolution: "BLANKFLAG" application-specific information has been added. If "BLANKFLAG=true" is set on the attribute application-specific information, then the value for CxBlank is interpreted as "" in the WHERE clause. |
|
2 | 68865 | JR25076 | UNVL=NULL with null dates are processed differently between the Create and Update verbs. |
Symptom: According to the Adapter for JDBC documentation, the "UNVL=NULL" application-specific information should take effect when the attribute value is CxIgnore (null). However, for the Create operation, this application-specific information takes effect when the attribute value is CxBlank (""),which is incorrect. |
Resolution: For the Create operation, "UNVL=NULL" application-specific information takeseffect when the attribute value is CxIgnore. So that the Create and Update verbs have the same behavior, both work with CxIgnore for "UNVL=NULL" application-specific information. |
|
3 | 85595 | JR24704 | When running a stored procedure with an integer input parameter in JDBC, an error message is displayed. |
Symptom: When running the stored procedure, the adapter checks to see whether the value of the input parameter matches its data type. But because of an error in the validation code, when the data type is Integer, the adapter generates an error. |
Resolution: Code has been added so that the value's data type is appropriately checked. |
|
4 | 85363 | JR24549 | When the PingQuery fails, the adapter does not stop. |
Symptom: When the adapter processes a business object with the verb set to Update, it does not stop and restart even when the PingQuery SQL statement fails. |
Resolution: When the PingQuery SQL statement fails, the adapter sets the return status to -2, so that the Adapter Framework stops the adapter and restarts it correctly. |
|
5 | 85144 | JR24427 | UNVL does not work with the Update verb when the attribute data type is Integer, Float, and Double. |
Symptom: When you use UNVL on an attribute, set CxIgnore as a value of this attribute, and set the verb to Update, the adapter tries to parse the value of CxIgnore (null) as a number. As a result, a NumberFormatException exception occurs. |
Resolution: When finding UNVL is used, the value of the attribute is CxIgnore and the verb is set to Update, the adapter does not parse CxIgnore. The adapter uses the value of application-specific information UNVL to continue its work. |
|
6 | 84876 | JR24278 | When the adapter generates a parsing error, it does not include the attribute name in the error message. |
Symptom: The adapter does not include the attribute name in the error message when an error is encountered while parsing the attribute. |
Resolution: The error message includes the attribute name to help with problem determination. |
|
This table lists the enhancements and fixes in fix pack version 2.6.5. |
Enhancements |
1 | 67678 | | The getVersion() implementation for the adapter needs to be updated. |
Symptom: The adapter version should be implemented from the manifest file rather than from a static variable set in the code. |
Resolution: This update has been made. |
|
2 | 83827 | | Support on Solaris 10 platform is needed. |
Symptom: The adapter should be supported on the Solaris 10 platform. |
Resolution: Support is now provided. |
|
3 | 83686 | | References to data direct drivers in the JDBC ODA start scripts should be removed. |
Symptom: The data direct driver JAR files in the class path need to be removed from the start scripts of the JDBC ODA. |
Resolution: The data direct driver references have been removed. You must add the appropriate JDBC driver files into the class path. |
|
Fixes |
1 | 67959 | | There are two positions where the trace message number 32016 is incorrectly used. |
Symptom: There are two positions where trace message 32016 is used by mistake; 32017 is the correct trace message number. |
Resolution: Trace message 32016 has been replaced with 32017 in these two positions. |
|
2 | 67929 | | The message of a returned instance of the class CWConnectorExceptionObject is not correct. |
Symptom: When the adapter handles a service request that fails due to an exception, it retries the operation. If the second attempt to handle this service request fails again, the message of the returned instance of class CWConnectorExceptionObject is incorrect. |
Resolution: This defect has been fixed. The message for the second failure is now correct. |
|
3 | 82879 | JR22976 | The adapter receives an Invalid Ref-Cursor error when doing a RetrieveSP operation. |
Symptom: When trying to retrieve a business object from a table using a stored procedure that returns a result set through a cursor, the adapter encounters an Invalid Ref-Cursor error from Oracle. |
Resolution: This defect has been fixed. |
|
4 | 74554 | JR22906 | java.sql.SQLException error occurs: Not enough memory with CLOB in SP. |
Symptom: The adapter needs more memory to read and store CLOB type data. |
Resolution: This defect has been fixed. The adapter has optimized its memory allocation for CLOB type data. |
|
5 | 74241 | JR23258 | Application-specific information UNVL=NULL does not work correctly. |
Symptom: When the application-specific information UNVL=NULL is specified, and the value of this attribute is null, the adapter ignores the attribute and therefore cannot update its value to null in the database as expected. |
Resolution: This defect has been fixed. |
|
6 | 74237 | JR22731 | The adapter generates an SQL sentence such as "where ... xxx is null" that results in a CLI0612E exception. |
Symptom: For the RetrieveByContent verb, the adapter tries to set the redundant attribute value into a prepared statement when generating the SQL Query 'where ... is null'. |
Resolution: This defect has been fixed. |
|
7 | 74225 | JR22760 | The NUMBER field in the Oracle database is converted into a string by the ODA. |
Symptom: The ODA does not use the separator that is needed between the precision and decimal positions. Also, the arithmetical operator +/- does not have any space. |
Resolution: The length will be extended by two for those columns with the Decimal data type. |
|
8 | 67361 | | The adapter prints an incorrect error message when there is no record in the UID table. |
Symptom: When there are no records in the UID table, the adapter prints an error message saying that there are problems in the database connection. |
Resolution: This defect has been fixed and the adapter now prints an appropriate error message. |
|
9 | 83714 | JR23663 | The adapter writes an incomplete business object to the Oracle database. |
Symptom: If the adapter receives a shutdown message during a transaction, it performs a connection close operation. But for the Oracle database, the connection close operation requires that a commit operation, not a rollback operation, be performed before the close operation. Otherwise, the transaction may result in inconsistent data in the Oracle database. |
Resolution: When receiving a shutdown message, to ensure that the data in the database remains consistent, the adapter explicitly performs a rollback operation. |
|
10 | 83595 | JR23449 | DB2(R) sequence support for the adapter has a bug. |
Symptom: Sequence is supported in DB2 8.0 and later; therefore, the adapter supports sequence for DB2 8.0 and later. However, the correct SQL statement for the DB2 sequence cannot be generated. |
Resolution: The defect has been fixed and the correct SQL statement for the DB2 sequence is generated. The correct SQL statement will be used to get the value from the DB2 sequence for the UID in the adapter. |
|
11 | 68092 | JR23653 | A java.lang.ClassCastException exception is generated when setting the application-specific information PSC to true. |
Symptom: When setting the application-specific information PSC to true and running a stored procedure, the adapter generates a java.lang.ClassCastException exception. This is a bug in the prepared statement cache for the stored procedure. |
Resolution: A prepared statement is declared for the stored procedure SQL sentence first. Then this prepared statement is cast into a callable statement. |
|
This table lists the enhancements and fixes in fix pack version 2.6.4. |
Enhancements |
There are no enhancements in this fix pack. |
Fixes |
1 | 73915 | | Code missing from fix pack code line. |
Symptom: When code was merged from an interim fix code line to fix pack code line, a small block of code was deleted from the class JDBCDBManager. |
Resolution: This issue has been fixed. |
|
This table lists the enhancements and fixes in fix pack version 2.6.3. |
Enhancements |
1 | 70569 | | References to data direct drivers in the adapter start scripts should be removed. |
Symptom: The data direct driver JAR files in the class path need to be removed from the start scripts of the adapter. |
Resolution: The data direct driver references have been removed. You must add the appropriate JDBC driver files into the class path. |
|
Fixes |
1 | 71314 | JR21597 | An extra where clause and "is null" support |
Symptom:
The "is null" support does not work when there is more than one attribute in the extra where clause, using Retrieve verb application-specific information.
|
Resolution: A proper query using multiple attributes in verb application-specific information is used. |
|
2 | 71139 | JR21480 | Blank values in event keys used to retrieve business objects using "is null" clause |
Symptom: When an event has some keys set as null, the adapter does not generate the SQL query with the "is null" clause. |
Resolution: The use of CxBlank in the event object keys is fixed, and the adapter now builds the "is null" clause properly when polling. |
|
3 | 71391 | JR22459 | Cursor leak causes max cursors to exceed the set limit. |
Symptom: A cursor leak causes the max cursors to exceed the set limit. |
Resolution: The empty ResultSet is now closed when it is returned from a stored procedure call. |
|
4 | 72378 | JR22444 | Using blank values in keys of the business object for retrieval purposes using the "is null" clause |
Symptom: When the adapter processes an incoming business object with some keys designated as null, it does not generate the query with the "is null" clause. |
Resolution: Changes have been made to the adapter to provide the value CxBlank in the key value, so that the adapter builds the "is null" clause correctly. |
|
5 | 72988 | JR22446 | Output parameters returned when a function is run in the database are not retrieved in the correct order. |
Symptom: An incorrect index value is being used to retrieve the output parameters of type String. |
Resolution: This defect has been fixed. |
|
6 | 67474 | JR22154 | If CloseDBConnection is set to true, the adapter waits indefinitely to fetch a connection. |
Symptom: When the maximum number of database connections is reached, the thread exits the fetchConnection only when a connection is released and the thread is notified. If CloseDBConnection is set to false, notify is being called, but when CloseDBConnection is set to true it is not called. |
Resolution: This defect has been fixed. |
|
7 | 67496 | JR22431 | The adapter does not allow data larger than 32k to be inserted for input parameters of stored procedures. |
Symptom: No special handling is done for input parameters to stored procedures that are of type CLOB. |
Resolution: This defect has been fixed. |
|
8 | 45825 | JR22463 | The startup script for Windows contains an extra pause statement. |
Symptom: There are two pause statements in the startup script for Windows(R). |
Resolution: The extra statement has been removed. |
|
9 | 61153 | JR21014 | RetrieveSP is not run for child business objects when UseDefaultsForPolling is set to true. |
Symptom: If the value of the attribute RetrieveSP is set to CxBlank and UseDefaultsForPolling is set to true, the stored procedure application-specific information retriever does not parse stored procedure application-specific information. This happens when UseDefaultsForPolling is set to true. |
Resolution: This defect has been fixed. |
|
10 | 66540 | | The adapter logs an error when setting TimingStats to the default. |
Symptom: The TimingStats property is missing from the template file. |
Resolution: This defect has been fixed. |
|
11 | 67621 | JR22378 | The adapter fails to handle CLOB data with a length between 4000 and 4096. |
Symptom: The check for the size of CLOB data is incorrect. |
Resolution: This defect has been fixed. |
|
12 | 71729 | JR21809 | The JDBC ODA version 2.6.2 does not work with business object designer in the Adapter Framework. |
Symptom: Version 2.4 of the Adapter Framework is not enabled for bidirectional script. Because version 2.6.2 of the JDBC ODA has bidirectional-enabled features, it fails when it is used with version 2.4 of the Adapter Framework. |
Resolution: The fix has been made to the JDBC ODA to check for bidirectional-enablement in the Object Discovery Kit and make calls appropriately to ensure compatibility with earlier versions. |
|
13 | 72255 | JR21999 | The adapter does not retrieve rows with empty CLOB columns. |
Symptom: When a CLOB type variable is null, a NullPointerException exception is generated. |
Resolution: The adapter now includes a proper check for a null value. |
|
14 | 73153 | JR22462 | Retrieving n cardinality business objects with the Progress database fails. |
Symptom:
If a close operation is issued on an already closed ResultSet, the Progress database generates an exception.
|
Resolution:
The adapter has been corrected to ensure that close operation is called only once.
|
|
15 | 73466 | JR22458 | RetrieveSP appears to be called but does not return a result set. |
Symptom: The AfterRetrieveSP stored procedures are called before the output parameters for the RetrieveSP store procedure are completely processed. |
Resolution: This defect has been fixed. |
|
16 | 73476 | JR22447 | Support for the long int data type in stored procedures is missing. |
Symptom: When the adapter processes parameters of stored procedures, the DriverSupportForLong property is not being used. |
Resolution: This defect has been fixed. |
|
This table lists the enhancements and fixes in fix pack version 2.6.2. |
Enhancements |
There are no enhancements in this fix pack. |
Fixes |
1 | 61712 | JR21196 | Adapter memory leak when the value for CloseDBConnections is true |
Symptom: An adapter memory leak occurs when the value for CloseDBConnections is set to true. |
Resolution: A check is performed to see whether the value for closeDBConnection is set to true. If the value is set to false, the adapter creates a hash table entry of the connections, for use in the prepared statement cache. |
|
2 | 45017 | JR21320 | Copy Attributes does not propagate values to a child business object. |
Symptom:
For a child business object with an attribute having the following application-specific information values: PH=true:CA=..[ParentAttrName], the appropriate value can be copied to the child attribute correctly. But the overall operation will fail. This is due to improper handling of the PH application-specific information attribute.
|
Resolution: This defect has been fixed. |
|
3 | 61625 | JR21339 | When traversing, the adapter does not return the accurate error. |
Symptom: If a non-required, ownership child was not found on retrieval, the connector generates an error message. |
Resolution: This defect has been fixed. |
|
4 | 44568 | JR21317 | Date processing with stored procedure causes a null pointer exception. |
Symptom: Date processing with a stored procedure causes a null pointer exception. |
Resolution: This defect has been fixed. |
|
5 | 66453 | JR21272 | The table xworlds_batch_events, created by using archive_table_oracle.sql script, is not used. |
Symptom: The table xworlds_batch_events, created with the archive_table_oracle.sql script, is not used. |
Resolution: The xworlds_batch_events table is no longer created and has been removed from the script archive_table_oracle.sql. |
|
This table lists the enhancements and fixes in fix pack version 2.6.1. |
Enhancements |
There are no enhancements in this fix pack. |
Fixes |
1 | 58941 | JR20679 | Timing Stats does not print the method name. |
Symptom: The method name is being passed to the utility method that traces the message, but it is not being included in the trace message. |
Resolution: This defect has been fixed. |
|
2 | 60212 | | The foreign key of the child object is not populated with the new identity column value from the parent. |
Symptom: After the identity value is generated in the table in the database, it is not being retrieved from the database when the database type is DB2(R). |
Resolution: This defect has been fixed. |
|
3 | 44732 | | The JDBC ODA strips the underscore ('_') character from business object attribute names. |
Symptom: The JDBC ODA strips the underscore character ('_') from business object attribute names because it is considered a special character. |
Resolution: The underscore character is now included as part of the business object attribute. |
|
|