SI53928 - RDARS-ONDWEK-UNPRED Sudden OD Server disconnect issue with d

TYPE PROGRAM  REL  NUMBER   MIN/MAX  OPTION
---- -------- ---  -------  -------  ------
DIST 5770RD1  710  SI49233   NONE     0010



NOTICE:
-------
Application of this PTF may disable or render ineffective programs that
use system memory addresses not generated by the IBM translator,
including programs that circumvent control technology designed to limit
interactive capacity to purchased levels.  This PTF may be a prerequisite
for future PTFs.  By applying this PTF you authorize and agree to the
foregoing.

This PTF is subject to the terms of the license agreement which
accompanied, or was contained in, the Program for which you are obtaining
the PTF.  You are not authorized to install or use the PTF except as part
of a Program for which you have a valid Proof of Entitlement.

SUBJECT TO ANY WARRANTIES WHICH CAN NOT BE EXCLUDED OR EXCEPT AS EXPLICITLY
AGREED TO IN THE APPLICABLE LICENSE AGREEMENT OR AN APPLICABLE SUPPORT
AGREEMENT, IBM MAKES NO WARRANTIES OR CONDITIONS EITHER EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OR CONDITIONS OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON INFRINGEMENT,
REGARDING THE PTF.

The applicable license agreement may have been provided to you in printed
form and/or may be viewed using the Work with Software Agreements (WRKSFWAGR)
CL command.





APAR Error Description / Circumvention

-----------------------------------------------
In the extremely unlikely event that the OnDemand Object Server
becomes unavailable in the middle of a retrieval transaction
(ie. network failure, object server termination), there is a
scenario where ODWEK could return unintended data.  This also
assumes that the customer application would have ignored a
severe connection error, and continued to process requests (once
the network/object server was restored), despite these original
connection failures/errors.

The issue is that when a single ODWEK ODServer object is doing a
api retrieve() call to get the document data, and the document
data is currently streaming from the object server to the ODWEK
instance, if that streaming operation is interrupted by a server
cannot connect error, then ODWEK may have some/all of the
document data in temporary storage.

In this case, the customer recreate managed to disconnect the OD
Object Server in the middle of the document streaming (a
sub-second transaction in most cases), so that while we had some
document data returned, the streaming operation wasn't able to
complete.  ODWEK had assumed that if a connection failure error
was thrown, then we didn't have a connection to the server, and
no data was available to be retrieved.  In this case though, we
do have a partial/full document from the retrieve, as received
before the server was disconnected, and that data is not
properly cleaned up.

With that data still in temporary storage, the next retrieve
request made by that same ODWEK ODServer instance will be
appended to the buffer from the previous request.  The result is
that the enduser could see data from the previously interrupted
retrieve() call on that same ODServer.  If the application was
to terminate() the ODServer when the connection error occurred,
rather than just repeating the requests, this scenario could be
completely avoided.

CORRECTION FOR APAR SE59618 :
-----------------------------
The problem is fixed.

CIRCUMVENTION FOR APAR SE59618 :
--------------------------------
Customer application should terminate the ODServer when a server
connection error is determined, and not attempt to reuse the
ODServer when the connection errors occur.


Activation Instructions


None.




Special Instructions


********************************************************************
THE FOLLOWING ARE SUPERSEDED SPECIAL INSTRUCTIONS. IF THE SUPERSEDED
PTF HAS ALREADY BEEN APPLIED AND ITS SPECIAL INSTRUCTION FOLLOWED,
IT IS NOT NECESSARY TO FOLLOW THAT SPECIAL INSTRUCTION AGAIN.
********************************************************************

SPECIAL INSTRUCTIONS FOR SUPERSEDED PTF SI50491 :
=================================================

After applying the 9.0.0.2 Content Manager OnDemand PTFs:

1. If you are running the OnDemand Web Enablement Kit (ODWEK) servlet.
The ear file must be updated with the current 9.0.0.2 code and
redeployed. The files used in the ear file are located in the following
directories:
/QIBM/ProdData/OnDemand/www/applets
/QIBM/ProdData/OnDemand/www/servlets

2. If you are running the OnDemand Java APIs, The 9.0.0.2
ArsWWWInterface.class and ODApi.jar files must be implemented in your
code.  This may require recompiling or rebuilding files associated with
your application.  Please refer to the ODApiDoc.zip file. The Java API
files are located in the /QIBM/ProdData/OnDemand/www/api directory.

3.  The image and AFP plugin files should be reinstalled.  The plugin
files are located in the
/QIBM/ProdData/OnDemand/www/plugins directory.


Default Instructions

THIS PTF CAN BE APPLIED IMMEDIATE OR DELAYED.



Supersedes

PTF/FIX NO(S).  APAR TITLE LINE
--------------  ------------------------------------------------------------
   SI51621      RDARS-ONDWEK Upgrade ODWEK to server level 9.0.0.3
   SI50845      RDARS-ONDWEK-INCORROUT Java API issues error if using ARSWWW
   SI50491      RDARS-ONDWEK-INCORROUT Upgrade to server level 9.0.0.2
   SI49261      RDARS-ONDWEK-INCORROUT ODWEK - Upgrade to server level 9.0.0
   SI48581      RDARS-ONDWEK-INCORROUT CUSTOMER UNABLE TO VIEW PDF OBJECTS W
   SI46571      RDARS-ONDWEK-INCORROUT Upgrade ODWEK to 8.5.0.5 server level
   SI44993      RDARS-ONDWEK-INCORROUT LDVA certificate expiration
   SI43041      RDARS-ONDWEK-INCORROUT Update ODWEK IFS objects to server le
   SI38900      RDARS-ONDWEK-INCORROUT
   SI36367      ONDWEK - Upgrade to Server Level 8.4.1.3 - IFS Objects
   SI44537      RDARS-ONDWEK-INCORROUT Change ODApi.jar file to use java 1.5
   SI43040      RDARS-ONDWEK-INCORROUT Updates to ODWEK CGI and Servlet to 8
   SI43040      RDARS-ONDWEK-INCORROUT Update ODWEK API to server level 8.4.
   SI39942      RDARS-ONDWEK-INCORROUT  Updates for ODJavaAPIExamples file
   SI39330      RDARS-ONDWEK-INCORROUT  Updates for ODWEK API 8.4.1.3
   SI36352      ONDWEK - Update to Server Level 8.4.1.2 - API
   SI41393      RDARS-ONDWEK-INCORROUT PTF exit fails
   SI38681      RDARS-ONDWEK-INCORROUT Updates to ODWEK CGI and Servlet
   SI36349      ONDWEK - Update to Server Level 8.4.1.2 0 CGI/Servlet

Summary Information

System i Support