OS/2 Shareware BBS: 8 Other/08-Other.zip/capaepcl.zip/eclos2.txt

Text File | 2003-02-24 | 6KB | 139 lines

       Product: IBM CallPath Enterprise Client
       Version: 6.3.1
         Level: E2294
      Platform: OS/2
          Date: 16 October 2002
  Service File: eclos2.exe
       History: eclos2.hst
          Size: 3301473   (3.1Mb)


  Installation Instructions:
  --------------------------
    Download the self-extracting file, eclos2.exe, into a temporary directory.
    Execute it from the command line and follow the prompts.

    If you answered "Yes" to the backup query and wish to
    undo the service update, issue the following commands:

      <installdrive>:
      cd \
      <backupexe> -Qdr

    where <installdrive> is the drive letter on which product is installed
      and <backupexe> is the full path name of the backup self-extracting file.


  Fixes contained in this Service Package:
  ----------------------------------------

       Name: ER47483
       Date: 02 Oct 2002
    Library: 10667
    Symptom: An attempt to establish the 201st active connection results in
             a return code of TADS_RESOURCE_UNAVAILABLE (503).
    Problem: A table of 200 entries limits the number of active connections
             an application can have with the CEO client.
   Solution: Connection table size increased from 200 to 1000.

       Name: ER36013
       Date: 30 Nov 2001
    Library: 10196
    Symptom: An unexpected (undocumented) return code is received from
             TadsQueryServerList API.
    Problem: A return code variable was being checked prior to being set.
   Solution: Initialize the return code variable to 0.

       Name: APAR IC32243
       Date: 26 Nov 2001
    Library: 10169
    Symptom: On a CEO client, server, or daemon window (running in Windows
             environment), if a double-click is done on the system icon
             then the window is destroyed but the executable remains
             active.
    Problem: The default windows action was being taken which resulted in
             the close of the window but the process remained active. The
             use of the task manager was required to stop the executable.
   Solution: Have a double-click of the system icon work the same as if
             "Close" was chosen from the system menu.

       Name: APAR IC32262
       Date: 20 Nov 2001
    Library: 10157
    Symptom: The amount of memory used by csebserv and csebclnt continues
             to grow. Eventually, csebserv or csebclnt will run out of
             available memory and either abend or fail requests.
    Problem: Allocated memory was not being released. For each
             TadsQuerySysStatus request, 20 bytes remained allocated in
             csebserv and 40 bytes remained allocated in csebclnt.
   Solution: Free this memory once it is no longer needed.

       Name: APAR IC31537
       Date: 5 Sep 2001
    Library: 9850
    Symptom: On an AIX SMP system a core may occur on the first call to
             TadsConnectToServer. The error report shows a segment fault in
             the C++ library function __DoThrow.
    Problem: C++ try/catch logic was being used in passing return codes. In
             a multithreaded and multiprocessor environment a throw of an
             integer object occasionally produces a segment fault.
   Solution: Remove try/catch logic from the CPE API library (libcseb.a).
             Instead, the conventional means of passing and checking return
             codes is used.

       Name: APAR IC31187
       Date: 2 Aug 2001
    Library: 9649
    Symptom: To the user of JTAPI this problem shows up as events not being
             received or as requests timing out. The problem only occurs
             when the JTAPI daemon is running in an AIX system.
    Problem: During the start up of the JTAPI daemon, CSEBJTPI, hundreds of
             TadsSetEventMonitor requests may be issued. While these
             monitors are being issued the JTAPI daemon is not attempting
             to read from its event queue. If enough events are flowing to
             fill up the event queue before all the monitors are completed,
             then the CPE Client may time out the connection associated
             with this event queue and cancel the monitors. In this failure
             situation, the JTAPI daemon does not attempt to re-establish
             the cancelled event monitors.
   Solution: The time out limit used by the CPE Client in sending an event
             is being increased from 5 seconds to 10 seconds. If an event
             send times out, instead of closing the connection, the event
             is discarded but the connection remains open. The following
             text appears in the client log when an event is discarded:
             "Warning: IPCQueue <queue-name> is full ...1 event discarded".

       Name: APAR IC30786
       Date: 26 June 2001
    Library: 9500
    Symptom: After a network outage between a Callpath Enterprise client
             and server, an application that reopens a connection and
             registers for events may not receive events for which it is
             registered.
    Problem: The clean up processing associated with a broken Callpath
             Enterprise client to server connection may take over a minute
             to complete (mainly due to slow response from TCP/IP
             requests). If new event monitors are registered during the
             clean up period, they may inadvertently get cancelled by the
             clean up processing.
   Solution: Changed the logic in the Callpath Enterprise client to only
             clean up resources associated with connections that are active
             at the time of the network outage.


  Files contained in this Service Package:
  ----------------------------------------
    dll\cseblib.dll
    dll\csebnet.dll
    dll\csebmwin.dll
    dll\csebapi.dll
    dll\csebdmon.dll
    dll\libcpo04.dll
    bin\csebdbgw.exe
    bin\csebclnt.exe
    csebclnt.txt
    bin\cfgcfg.jar
    bin\cfgframe.jar
    bin\cpcfg.txt