PQ81150: THIS APAR ADDRESSES DEFECTS IN WEBSPHERE APPLICATION SERVER V5.0 FOR Z/OS.

 A fix is available

Obtain the fix for this APAR



APAR status
Closed as program error.

Error description
This APAR addresses defects in WebSphere Application Server
V5.0 for z/OS.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 V5.0 for z/OS                                *
****************************************************************
* PROBLEM DESCRIPTION: APAR PQ81150 addresses various defects  *
*                      in WebSphere Application Server V5.0    *
*                      for z/OS.                               *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
APAR PQ81150 addresses the following defects in
WebSphere Application Server V5.0 for z/OS:

(MD18090) Temporary files and directories are not being cleaned
up when applications are deployed. When applications are
deployed/exported/etc, temporary directories are often created
to hold intermediate files, then deleted when the task
completes. The directories used for this are named something
like /tmp/app_nnnnnn/...   On z/OS, these directories are not
being cleaned up and the following errors are logged -

ADMA6011I: Deleting directory tree /tmp/app_f7d46ec883
Trace: 2003/09/24 16:42:27.620 01 t=9CF170 c=UNK key=P8
  FunctionName: com.ibm.ws.management.application.AppUtils
  SourceId: com.ibm.ws.management.application.AppUtils
  Category: WARNING
  ExtendedMessage: ADMA0078W: Unable to delete file: /tmp/app_..
Trace: 2003/09/24 16:42:27.621 01 t=9CF170 c=UNK key=P8
  Description: Log Boss/390 Error
  from filename: ./bborjtr.cpp
  at line: 812
  error message: BBOO0221W ADMA0078W: Unable to delete file: ...

In the AppUtils.deleteDirTree() method, there exists logic to
prevent the deletion of any directories which are referenced as
a symbolic link from the directory to be deleted.

On z/OS, the /tmp directory itself is created as a symbolic link
(tmp -> $SYSNAME/tmp), therefore any temporary directory created
under /tmp will not be deleted by this logic.

(MD18114) wsadmin securityon command failed and
NullPointerException was thrown. JMXConnector was not
initializing Security Service in the Servant process causing
the securityon command to fail.

(MD18118) NullPointerException recieved in client while
utilizing an Iterator of a Collection which was obtained via a
finder in a previously commited transaction. When a lazy
collection is obtained in a specific transaction, and that
transaction is then committed, the facilities that enable lazy
collection support on the server are terminated as part of tran
completion. Lazy collections have an internal size associated
with them that when exhausted causes the collection to go remote
to get the next chunk of collection data. As part of the tran
completion cleanup of the lazy collection facilities on the
server, orb disconnect is driven on the object that connects the
client side of the collection to the server side. On the client
side, once the internal size is exhausted, the collection
support attempts to go remote to retrieve the next chunk of
object data and is successful when it should not have been. This
is due to the fact that the proxy for that object is still
availiable and can be used. On the server side, with the
collection objects terminated, including any jdbc cursors
associated with the collection, a NullPointerException is
raised.

(MD18121) When running the "Security Domain configuration"
option, if the user type in a value for KEYMASK, the value is
not saved to the Security Domain variable data set. The problem
is that the dialog is missing a VPUT statement in the BBOWSD12
to save the KEYMASK value.

(MD18124) Transaction recovery fails for datasources using a
component managed alias. During transaction recovery,
connections to the underlying datasource need to be created
based on serialized data. Currently, if a component managed
alias is defined on the WebSphere datasource, this value is not
stored with the serialized data and therefore we are unable to
find a user name and password with which to obtain the
connection.

If this problem occurs, an exception similar to the following
will appear in the joblog of your application servant region
along with a message specific to your underlying datasource
indicating that a user name and password is needed to obtain
a connection:

DSRA8100E: Unable to get a XAConnection from the DataSource.
at com.ibm.ws.rsadapter.exceptions.DataStoreAdapterException
  .<init>(DataStoreAdapterException.java:244)
at com.ibm.ws.rsadapter.exceptions.DataStoreAdapterException
  .<init>(DataStoreAdapterException.java:171)
at com.ibm.ws.rsadapter.AdapterUtil
  .createDataStoreAdapterException(AdapterUtil.java:191)
at com.ibm.ws.rsadapter.DSConfigurationHelper
  .getPooledConnection(DSConfigurationHelper.java:694)
at com.ibm.ws.rsadapter.spi.WSRdbDataSource
  .getPooledConnection(WSRdbDataSource.java:440)
at com.ibm.ws.rsadapter.spi.WSManagedConnectionFactoryImpl
  .createManagedConnection
  (WSManagedConnectionFactoryImpl.java:566)
at com.ibm.ejs.j2c.J2CXAResourceFactory
  .getXAResource(J2CXAResourceFactory.java:230)
at com.ibm.ejs.jts.jta.recovery.XARecoveryData
  .recover(XARecoveryData.java:602)
at com.ibm.ejs.jts.jta.recovery.XARecoveryManager
  .xaRestartRecovery(XARecoveryManager.java:514)

(MD18126) Control region gets abend 0C4 reason code 10 in method
comm_inbound_response. comm_inbound_response needed to drive a
locate. The response for the locate came back on another thread
and deleted the orbr object before comm_inbound_response
completed. The call to severeErrorDetected in
comm_inbound_response needs the orbr object.

External symptom:

DUMP TITLE=COMPON=WEBSPHERE Z/OS,  COMPID=5655I3500,ISSUER=BBOR
          LEXT,ABEND IN BBOBOA  /comm_inbound_response

(MD18142) Interoperability between a z/OS client and a Windows
server fails with SECJ0053E or a CEEDUMP/JAVADUMP.

Three interoperability problems between a z/OS client and a
Windows server.
1. Windows server configured to SSL supported but not required.
SSL has not been setup on the client. The request failed with
system exception CORBA::UNKNOWN and a minor code of 4942fe86.
 he exception returned from the target server is :
com.ibm.websphere.csi.CSIException: SECJ0053E: Authorization
failed for /UNAUTHENTICATED
 . Windows server configured for TCPIP - no SSL. The request
failed with system exception CORBA::UNKNOWN and a minor code of
 942fe86. The exception returned from the target server is :
com.ibm.websphere.csi.CSIException: SECJ0053E: Authorization
failed for /UNAUTHENTICATED
3. Windows server configured with Identity Assertion not
supported. The request failed with a JAVADUMP and CEEEDUMP on
the client.
CEE3204S The system detected a protection exception
(System Completion Code=0C4). From entry point skipThisMech
(char**,unsigned short,char*,char*) at statement 2434
at compile unit offset +00000530 at entry offset +00000530
at address 20756438

(MD18145) WebSphere Distributed clients can experienced problems
demarshalling parameters when driving a request directly to the
Daemon. The Daemon would marshal a forwarding IOR in the
response, but would also include an improper IBM Partner Version
service context, causing a mismatch in how parameters were
marshalled when the request is correctly directed to the correct
server.

(MD18148)  Using wsadmin stopserver, startserver completed with
timeout. wsadmin StopServer, startServer, stopServer immediate
commands completed with time out error which was related to SOAP
timeout The default soap request timeout value was set to 3
minutes which is not large enough when it comes to server
startup which might take few minutes.

(MD18155) This defect is for the WebSphere Distributed Rollup
of Distributed's code (level cf10337.06).
Problem conclusion
APAR PQ81150 fixes various defects in WebSphere Application
Server V5.0 for z/OS.

(MD18090) It was decided to add a flag to deleteDirTree(),
whereby if it is known that the directory to delete is a
temporary directory, the link checking is not performed.  Also
some extra cleanup logic was added to link checking process.

(MD18114) The JMXConnector code has been modified to initialize
the security service and that seemed to fix the problem.

(MD18118) Updated ClientDelegate to check whether or not the
object represented by the proxy object is still connected. If
not, code updated to throw a proper exception to indicate that
the object does not exist.

(MD18121) To fix this, the dialog panel BBOWSD12 will be update
to add a VPUT statement to save the KEYMASK value. With this
VPUT statement for KEYMASK, the value will saved to the Security
Domain variables save data set.

(MD18124) Component managed aliases are now serialized and
deserialized during transaction recovery.

(MD18126) Changed comm_inbound_response to not reference the orb
object if another locate was done.

(MD18142) The Windows server exported an IOR with SSL Integrity
required when SSL was only supported. The zOS client interpreted
the IOR to mean SSL is required. Since SSL was not configured
on the client, the client did not attempt to use this CSIv2
mechanism and sent an unauthenticated request to the server.
The client was updated to use a different method to check for
SSL required.
2. The Windows server exported an IOR with a malformed tag
for No SSL. This caused the zOS client to misread the IOR,
not use the CSIv2 mechanism and send an unauthenticated request
to the server. The client was updated to understand what was
exported in the tag.
3. The Windows server exported an IOR with no Identity
Assertion and multiple CSIv2 mechanisms. The client failed
to update a pointer correctly when attempting to read the next
mechanism, resulting in a misread of the tag such that it
caused an abend. The client was updated to reset the pointer.

(MD18145) The IBM PartnerVersion service context is not
marshalled in the Daemon's outbound response.

(MD18148) Support has increasing the default soap request
timeout value in the soap client.props file will fix the timeout
issue.

(MD18155) This defect is for the WebSphere Distributed Rollup
of Distributed's code (level cf10337.06). The defects that it
addresses are:


PQ73754     mBean documentation missing information and
            broken

PQ74729     WRITEBEYONDCONTENTLENGTHEXCEPTION

PQ74731     ANT WSJSPC TASK DOES NOT USE "CLASSPATH" OR
            "CLASS"

PQ74820     SYNC IS STARTED BEFORE DISCOVERY PROCESS

PQ75055     J2C TO HANDLE THE CREDENTIAL/SUBJECT CHECKING FOR

PQ75365     JMSMessageQueueOverflowException:   using memory

PQ75469     CLASSES NOT FOUND WHEN A SHARED LIBRARY IS CREATED

PQ75491     Benign SECJ4046E occurs in admin console when tryi

PQ75639     Customer wishes to use own HttpServletRequestWrapp

PQ75656     UpdateInstaller needs to be resynchronized to work

PQ75698     With J2 security  .sun.net.www.protocol.jms

PQ75699     IllegalStateException when content-length is set.

PQ75714     HP_UX:IllegalStateEx -Save after import key the se

PQ75715     FIPS failing if java.security file does not have

PQ75723     Web browser allows multiple LTPAToken cookies to b

PQ75729     Password for a WebSphere MQ Queue Destination show

PQ75742     Anchor tag loses its functionality with encodeURL

PQ75766     Server fails to start on Solaris 9

PQ75794     TID Export.

PQ75805     AP_HTTP_METHODONLY RETURNS HTTP USING WAS50PLUGIN

PQ75813     WSAS updateInstaller can update product when AppSe

PQ75815     NULL RETURNED WHEN ACCESSING THE RESOURCE FILE (.P

PQ75913     Performance Regression in interruptible processes

PQ75913     Use of JROM in WSGW renders WSIF and WSGW unusable

PQ75913     UnsupportedOperationException using WSGW target sv

PQ75913     NullPointer exp in WSIFOperation_JCA when message

PQ75913     WSWS3073E Error Serialization cannot occur

PQ75936     WEBSPHERE PLUGIN DOES NOT HANDLE HTTP REQUEST OR R

PQ75947     Plugin fails to load when PrimaryServer defined

PQ75986     BVT: webcontainer except from start server and tra

PQ75991     SVT:Memory leak in IHS 2.0 plugin with ESI enable

PQ76051     MQ QCF CONFIGURATION PAGE HOST AND PORT FIELDS CAN

PQ76091     FVT: ND PTF2 Share Type PUSH_PULL fails outside of

PQ76144     SVT: error HTTP status code wrong

PQ76163     Problems associating roles to users when using Jav

PQ76174     304 response corrupts input stream used by next re

PQ76204     Unable to view JDBC provider on larger node and wh

PQ76270     SVT: urlprotocols.jar not found in server runtime

PQ76310     NullPointerException when processing received Sess

PQ76369     security not handling wild cards for port numbers

PQ76402     TransactionMBean returns incorrect transaction sta

PQ76405     Improve diagnostics for prepare/complete XA errors

PQ76408     No IllegalStateException when doing JSP forward af

PQ76432     Synchronization breaks when J2C JAAS authenticatio

PQ76483     Skip HTTPS Transport when there is error in loadin

PQ76486     Serviceability Enhancement, Aged timeout implement

PQ76508     WS_ANT FAILS TO ADMINISTRATE A WSINSTANCE NODE.

PQ76513     updateInstaller reports incorrect version in selec

PQ76548     IHS crashes when server w/ affinity has weight set

PQ76648     SVT: LI1957 (IBMJSSEFIPS) not supported on OS/400

PQ76693     GLOBAL WEBCONTAINER SETTING REGEN IMPROPERLY

PQ76707     JAVA.LANG.ILLEGALARGUMENTEXCEPTION THROWN DURING J

PQ76727     SYMPTOM: CORES WHILE IN IBM HTTP SERVER SSL MODULE

PQ76729     APPLICATIONS HANG DUE TO HANDLING OF CONTENT LENGT

PQ76758     5.02 lost functionality as opposed to 5.01 in term

PQ76788     FVT: Login popup window is blank or in-active.

PQ76794     TrustMode is optional, but when not specified, a N

PQ76804     addNode.sh command does not return if ran from rsh

PQ76805     please add the same changes, added in d141205 for

PQ76808     JDK 141 - changes to support server on non-IBM JDK

PQ76810     Root exception is being propogated to pure client

PQ76836     Denial of Service attack

PQ76836     Denial of Service attack

PQ76837     CLASSCASTEXCEPTION ON V5.0.1 WHEN WEBSERVICES INVO

PQ76886     Error 313 binaryTransfer: cannot set perms when us

PQ77010     V5: WSTEMPDIR keeps growing in size.

PQ77058     Unable to parse plugin when more HTTPS transports

PQ77059     PLUGIN NOT DOING ANEXACT MATCH FOR THE JSESSIONID

PQ77105     Loading plugin into Apache 2.0 fails with unresolv

PQ77142     SERVLETREQUESTCONTEXT IS NOT CLONED FROM ASYNCBEAN

PQ77217     Add EJBContainer Collaboration to the ExtHelper

PQ77261     Default certificates will expire on 01/15/2004.

PQ77329     Re-starting an EAR more than once causes an EJB We

PQ77357     PROBLEM WITH VERSION 4 DATASOURCE CLEANING UP LTC.

PQ77502     EEX PTF2 fails install based on Update Wizard

PQ77508     WSADMIN SCRIPT THAT WORKED FOR 5.0.0 AND 5.0.1 FAI

PQ77548     Only one role name is showing under the Authorizat

PQ77576     5.0.2 JSP session.setAttribute() replace fails

PQ77636     WSWS3185I error using WSDL2Java.bat from WSAS 5.02

PQ77755     TCK 101 IFIX FAIL: J2W Exception Mapping

(MD18290) This is an in support of defect for defect MD18275,
shipped in cumulative fix W502000. See defect MD18275,
documented in APAR 
PQ81152, for details.

APAR PQ81150 is associated with SERVICE LEVEL W502000 of
WebSphere Application Server V5.0 for z/OS.
Temporary fix Comments
APAR information
APAR number PQ81150
Reported component name WEBSPHERE FOR Z
Reported component ID 5655I3500
Reported release 500
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2003-11-19
Closed date 2003-12-07
Last modified date 2004-02-09

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:
UQ82900

Modules/Macros
BBOMSCSS BBORFPLU BBOSTMS BBOSTOS BBOSTXS BBOTOTS
BBOWHJUS BBOZ1114 BBOZ1115 BBOZ1200 BBOZ1219 BBOZ1314
BBOZ1340 BBOZ1344 BBOZ1345 BBOZ1359 BBOZ1467 BBOZ1475
BBOZ1477 BBOZ1478 BBOZ1492 BBOZ1500 BBOZ1508 BBOZ1512
BBOZ1522 BBOZ1529 BBOZ1530 BBOZ1551 BBOZ1561 BBOZ1569
BBOZ1589 BBOZ1592 BBOZ1596 BBOZ1601 BBOZ1610 BBOZ1613
BBOZ1614 BBOZ1617 BBOZ1623 BBOZ1631 BBOZ1635 BBOZ1636
BBOZ2561 BBOZ2563 BBOZ2642 BBOZ2643 BBOZ2991 BBOZ2992
BBOZ3007 BBOZ3026 BBOZ3847 BBOZ3862 BBOZ4238 BBOZ4249
BBOZ4251 BBOZ4268 BBOZ4271 BBOZ4273 BBOZ4378 BBOZ4503

Publications Referenced

Fix information
Fixed component name WEBSPHERE FOR Z
Fixed component ID 5655I3500

Applicable component levels
R500 PSY UQ82900    UP03/12/15 P F312

  Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.


Document Information


Current web document: swg1PQ81150.html
Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server for z/OS
Operating system(s):
Software version: 500
Software edition:
Reference #: PQ81150
IBM Group: Software Group
Modified date: Feb 9, 2004