The patch note contains the following sections:
This patch contains the following revisions since the last maintenance
release:
|
Available as of
Version |
CR Number / APAR
Number |
Description |
|
5.6.2 |
BGTRK00071620 |
When the Event or Output directories have an extra blank on
the MO, the JText adapter would not recognize the directory. The problem has
been rectified. The directories would be recognized now for leading and
trailing spaces. |
|
5.6.2 |
BGTRK00055201 |
If event datahandler was not included during request processing, output file would not get written to the output directory. Output datahandler property alone suffices during request processing. This issue has been resolved. Now it is not necessary to include event datahandler while request processing. |
|
5.6.2 |
BGTRK00055373 |
The parseNextToken functionality of ConnectorUtil would fail if the first character of the EndBODelim is present in the content of the event file.This problem has been fixed in CwDataHandler patch version 2.6.1. |
|
5.6.2 |
BGTRK00071561 |
JText
adapter would access an event file and throw a file-lock warning for its own
lock. The same has been rectified and the adapter now throws a warning when the
file is locked by external non-adapter processes. |
|
5.6.2 |
BGTRK00072218 |
JText adapter would crash
and restart when zero-byte files with no extension is encountered. The issue
has been fixed. If the event extension is .in(for eg.), then the files with
no extension will not be polled irrespective of their size. The zero byte
files with .in extension will be polled and archived as .damage. |
|
5.6.2 |
BGTRK00072220 |
JText
adapter would poll successfully for a while, then make poll rounds, but not pickup
event files. The issue was found both with mapped drives and the local
drives. The adapter no more gets into such a loop. The issue has been fixed.
JText connector would reach to the 100% CPU mode and freeze during polling
on HP-UX.The above fix has rectified this issue as well. |
|
5.6.2 |
BGTRK00048648
|
While polling/request
processing in the FTP mode if the is being fetched from a machine which is in
Japanese locale, the timestamp of the file would get appended to the name of
the file. This has now been resolved in commons-net-1.1.0.jar package. |
|
5.6.2 |
BGTRK00070670
|
If the file permission of
the event folder being polled by the adapter is read-only, the adapter would pick-up
the file for event processing, but would fail to delete it subsequently. In
this scenario, a warning message would not get logged. This has now been
rectified. |
|
5.6.2 |
BGTRK00071211 |
When the adapter is trying
to poll an event file being accessed by another program, it would fail to
archive the file and go into an infinite loop causing 100% utilization of
CPU. Checking for third-party lock and generating a warning message have
rectified the problem. |
|
5.6.2 |
BGTRK00070672 |
Whenever the adapter tries
to access an event file even as it is being written to the event directory by
a third-party application, the adapter would throw a ‘FileNotFound’
exception. The problem has been resolved by check for lock on event files. |
To perform an upgrade to this version of the connector add, replace, or
remove the following files and directories as indicated:
|
For Connector Version |
Platform [WIN;UNIX] |
Add / Replace / Remove |
File (Starting from %CROSSWORLDS%/$CROSSWORLDS) |
|
5.6.2 |
Win;Unix |
Replace |
connectors\JText\CWJText.jar;connectors\JText\Dependencies/commons-net-1.1.0.jar; |
February 25, 2005 04:00 PM
© 2003-2005 IBM Corporation. Proprietary and Confidential. All Rights Reserved.