| This table lists the enhancements and fixes in fix pack version 5.6.4.3IF. |
| Enhancements |
| There are no enhancements in this fix pack. |
| Fixes |
| 1 | 87935 | | Problem with FTP operations after upgrading to Jtext v5.6.4 |
| Symptom: When upgraded to JText v5.6.4, there is a problem faced with FTP operations. |
| Resolution: The issue was found in a third party jar used for FTP operations. The replacement of the existing jar provided with this Interim fix fixes the issue. |
|
| This table lists the enhancements and fixes in fix pack version 5.6.4. |
| Enhancements |
| There are no enhancements in this fix pack. |
| Fixes |
| 1 | 67282 | JR22071 | The adapter restarts after encountering an Internal error: Exception ::com.crossworlds.DataHandlers.Exceptions.CW_EndOfBOException: Already reached end of BO while expecting more token |
| Symptom: When the EndBODelimiter contains the character EOL, the adapter restarted after encountering an internal error exception. |
| Resolution: The adapter validates the EndBODelimiter 'EOL' along with a second delimiter and writes individual business objects based on the delimiter to the respective files. |
|
| 2 | 68261 | JR24097 | If the target FTP disk is full and a remote append is executed, the adapter does not return an error. |
| Symptom: If the target FTP disk is full and a remote append is executed, the adapter does not return an error. |
| Resolution: The adapter returns an error message to InterChange Server indicating that the flow failed. |
|
| 3 | 68477 | JR24317 | When the FileSeqEnable attribute is set to true, the adapter writes an extra new line. |
| Symptom: When the FileSeqEnable attribute is set to true, the adapter writes an extra new line to the output file. |
| Resolution: The adapter now Writes only one new line character to the output file when the attribute FileSeqEnabled is set to true. |
|
| 4 | 84140 | JR23530 | The adapter fails on requests with Dynamic MOs. |
| Symptom: The adapter fails on requests with Dynamic MOs. The code assumes that the JText object would be the First business object level application-specific information. |
| Resolution: An extra check is now included to handle the different ways that the business object level application-specific information can be specified.
|
|
| 5 | 83930 | JR23875 | When reconnecting, the adapter fails to process the first record. |
| Symptom: When the adapter tries to put a record to a file on the FTP Server and the timeout has been exceeded, the adapter fails to process the first record. |
| Resolution: The adapter checks for the connection before putting the first record, so it will not fail.
|
|
| 6 | 83283 | JR23646 | The adapter processes FTP files before it finishes downloading to the local directory. |
| Symptom: The adapter starts processing an FTP file before it finishes downloading to the local directory. |
| Resolution: The adapter checks to ensure that the file is readable and not locked and can be read.
|
|
| This table lists the enhancements and fixes in fix pack version 5.6.3. |
| Enhancements |
| 1 | 83528 | | Support for Red Hat Enterprise Linux 4.0. The adapter now supports Red Hat Enterprise Linux 4.0 ES (32-bit), Red Hat Enterprise Linux 4.0 AS (32-bit), and Red Hat Enterprise Linux 4.0 WS (32-bit) on WebSphere Business Integration Adapter Framework, version 2.6.0.5 and later. |
|
| 2 | 83529 | | Support for SUSE Linux Enterprise and Standard servers. The adapter now supports SUSE Linux Enterprise Server 9.0 (32-bit) and SUSE Linux Standard Server 9.0 (32-bit) on WebSphere(R) Business Integration Adapter Framework, version 2.6.0.3 and later. |
|
| 3 | 83530 | | Support for Solaris 10. The adapter now supports Solaris 10 (32-bit) on WebSphere Business Integration Adapter Framework, version 2.6.0.5 and later. |
| Symptom: The list of files that an installer changes is not known. |
| Resolution: A separate file, UpdateFilesList.txt, lists the files that are being changed by the installer. |
|
| Fixes |
| 1 | 67161 | JR23316 | An inappropriate error message is being generated. |
| Symptom: An inappropriate error message was being generated even though the adapter was functioning correctly. |
| Resolution: The problem with an error message has been corrected. |
|
| 2 | 71317 | JR23225 | A parsing error occurs during polling. |
| Symptom: A parsing error occurs when the adapter polls an input file that contains multiple business objects separated by an EndofBODelimiters marker. |
| Resolution: The parsing error has been corrected. |
|
| 3 | 72716 | JR23381 | The adapter fails to pick up files from the remote AS400 FTP server. |
| Symptom: While trying to download the Fixed-width file(s) from the AS400 FTP
server using the adapter, it creates a 0 KB local event file.
Also, the created file name is different from the original file name,
in that the first character of the original file name is
missing. |
| Resolution: The fix validates the listing of the files on AS400 FTP server and picks up the fifth token which is the actual filename. |
|
| 4 | 72774 | JR23322 | The adapter fails the first event after reconnecting to the FTP server. |
| Symptom: If the adapter running internally (in the intranet) receives an event from the InterChange Server and a connection timeout occurs, the adapter re-establishes the connection and then retries the event successfully. When the adapter encounters a firewall, it fails the first flow after a timeout and lets the following flows through successfully. |
| Resolution: The adapter has been modified to work with firewalls by enabling the socket to be alive. |
|
| 5 | 73905 | JR23002 | When the meta-object value for LargeObject is false, the adapter generates an error after successfully processing an event. |
| Symptom: A binary file with multiple events is not processed correctly.
The first event is archived correctly (with .SuccessArchiveExt), however
the adapter agent throws an exception, and goes into a restart. Then it
processes the same event again as if it is a new event. The same event is
archived again. The agent throws an exception and restarts. This continues
for ever. |
| Resolution: The fix includes check for existence of the archive file and validates if the archive file is opened. |
|
| 6 | 67718 | JR22623 | The adapter generates an error when the target FTP server is out of space. |
| Symptom: The adapter generates an error when the target FTP server is out of space. |
| Resolution: The fix throws an IOException create operation failed, which in turn sends a failure event to the broker. The file on the remote FTP server is deleted. |
|
| 7 | 67928 | JR23317 | JText fix pack 5.6.1 ReadMe needs a small correction |
| Symptom: JText fix pack 5.6.1 ReadMe file needs a small correction |
| Resolution: The ReadMe file for the JText fix pack version 5.6.1 states, in the upgrade instructions, that %INSTALLEDDIR%\repository\JText\MO_JTextConnector_Default.jar should be replaced. The JAR file name mentioned in the ReadMe file is incorrect. TheMO_JTextConnector_Default.jar should be MO_JText_Default.jar. |
|
| This table lists the enhancements and fixes in fix pack version 5.6.2. |
| Enhancements |
| There are no enhancements in this fix pack. |
| Fixes |
| 1 | 71620 | | No error is generated when an event directory path ends in a space. |
| Symptom: No error is generated when an event directory path ends in a space. When the Event or Output directories have an extra space on the meta-object, the adapter does not recognize the directory. |
| Resolution: The directories are now recognized as having leading and trailing spaces. |
|
| 2 | 55201 | | The adapter does not write a business object to a file. |
| Symptom: No files were being written to the output directory even though the adapter received the business object and did not generate any errors.
|
| Resolution: It is no longer necessary to include the event data handler during request processing. |
|
| 3 | 55373 | | The adapter does not write an error message to the log file. |
| Symptom: No error message is logged when the adapter fails to move a file from the staging directory to the event directory. |
| Resolution: An error message is now logged when such a failure is encountered. |
|
| 4 | 71561 | | The adapter locks its own event file and generates a warning. |
| Symptom: The adapter accesses an event file and generates a file-lock warning for its own lock. |
| Resolution: The adapter now generates a warning only when the file is locked by external non-adapter processes. |
|
| 5 | 72218 | | The adapter encounters a file archiver error. |
| Symptom: When the adapter encounters a zero-byte file with no extension, it crashes and restarts. |
| Resolution: If the event extension is .in, for example, the files with no extension are not be polled, regardless of their size. The zero byte files with a .in extension are polled and archived as .damage files. |
|
| 6 | 72220 | | The adapter for JText freezes during polling on HPUX. |
| Symptom: The adapter polls successfully for a while, then makes poll rounds, but does not pick up event files. This issue occurs both with mapped drives and the local drives. |
| Resolution: The adapter no longer goes into such a loop. |
|
| 7 | 48648 | | A problem occurs with the file name of a file retrieved by FTP from a workstation in the Japanese Locale. |
| Symptom: While polling or processing a request in the FTP mode, if the file is fetched from a workstation using the Japanese locale, the time stamp of the file is appended to the name of the file. |
| Resolution: The fix includes a new parser method to parse the listing of files in Unix machines. The parsing is done character by character. |
|
| 8 | 70670 | | The JText Connector does not issue an error or warning when a delete operation fails. |
| Symptom: If the file permission of the event folder being polled by the adapter is read-only, the adapter picks the file up for event processing, but fails to delete it later. When this occurs, a warning message is not logged. |
| Resolution: The fix involves checking for write permission on the event directory during archival, and if there is no write access, an error message is thrown for not being able to delete the event file. |
|
| 9 | 71211 | | The adapter freezes while polling the mapped drive. |
| Symptom: When the adapter polls an event file that is being accessed by another program, it fails to archive the file and goes into an infinite loop, causing 100 percent of the CPU to be used. |
| Resolution: The adapter now checks for a third-party lock and generates a warning message. |
|
| 10 | 70672 | | When a large file is obtained through FTP in the event folder and the connector is running, the following exception occurs: Unable to create workunit/java.io.FileNotFoundException |
| Symptom: When the adapter tries to access an event file as it is being written to the event directory by a third-party application, it generates a FileNotFound exception. |
| Resolution: The problem has been fixed through a check for locks on event files. |
|
| This table lists the enhancements and fixes in fix pack version 5.6.1. |
| Enhancements |
| 1 | 60885 | | The adapter has been enhanced to let you to switch between active and passive FTP mode. The attribute FTPMode, provided in the meta-object, can be set to either active or passive to switch between these modes. |
|
| Fixes |
| 1 | 58603 | | JText event delivery intermittently consumes 100 percent of the CPU while doing no work. |
| Symptom: During event polling, if a file is marked as damaged in the first run it continues to be marked as damaged in the subsequent runs too. Intermittently, the CPU usage shows 100 percent utilization. |
| Resolution: This defect has been fixed. |
|
| 2 | 60791 | | When the adapter hits the connection timeout, instead of simply reconnecting,
it gets the following error message: "ERROR : FTP response 421 received. Server closed connection" (421 = time out). |
| Symptom: With dynamic child meta-object and wrapper business object configurations, during a connection timeout the adapter does not retry connecting to the FTP server. |
| Resolution: The adapter now tries a maximum of 100 times to reconnect for any FTP transport related problems. |
|
| 3 | 60496 | | An event processing problem occurs with the Adapter for JText version 5.6.0. |
| Symptom: The parseNextToken functionality of ConnectorUtil fails if the first character of the EndBODelim is present in the content of the event file. |
| Resolution: This problem has been fixed in the CwDataHandler patch version 2.6.1. |
|
| 4 | 60787 | JR21455 | The adapter fails to pick up files from the FTP server. |
| Symptom: With the directory listing style set to DOS, the connector does not poll from the Microsoft IIS FTP server. |
| Resolution: The fix addresses this issue by correctly picking up the filename from the listing of files that is returned from a Windows 2000 FTP service. |
|
| 5 | 45566 | | 'Connector' should be removed from the '-n${CONNAME}Connector' for the Adapter for JText start scripts. |
| Symptom: 'Connector' should be removed from '-n${CONNAME}Connector' from the start scripts. |
| Resolution: 'Connector' has been removed from '-n${CONNAME}Connector' in the adapter start scripts, on both the Windows and Unix platforms. As a consequence, the connector meta-object has been updated and the updated repository is bundled in this fix pack. You will need to refresh the repository. |
|
|