PM08126: JCA ADAPTERS THAT ARE STARTED DURING SERVER STARTUP ON WEBSPHERE APPLICATION SERVER Z/OS MAY NOT HAVE THEIR END POINTS ACTIVATED

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• - Customer Environment is WebSphere App Server z/OS 6.1.0.25,
  WebServices Feature Pack 6.1.0.25, WPS 6.2.0.1, WebSphere
   Adapter for SAP 6.2.0.1.
  - Customer application includes the .rar file for the SAP
   Adapter, so the SAP Adapter is not installed into the WebSphere
   Application Server.
  - SAP Adapter Endpoints should be started during Server Startup
   by the 'container' code of the App. Server.  During the start
   of the server, the J2C code starts the endPoint Listeners.
   HAManager is not fully initialized at the time the J2C code
   is activating the endPoint, which causes the endPoint to NOT
   be activated.
  

Local fix

• You can set the custom property: 'enableHASupport' to false
  for the SAP Adapter packaged with your application.
  To do this, you go to the Admin Console:
  >> Enterprise Applications >> Application that has the SAP rar
  >> Manage Modules >> 'yourname SAPAdapter.rar >> 'Appname.IBM
  WebSphereAdapter for SAP Software with transaction support  >>
  custom properties
  ..
  You should see an 'name / value' pair for enableHASupport / true
  in the list of custom properties.
  You can change this value to 'false', then restart the server.
  ..
  NOTE that the above was changed when the server was a
  Stand-Alone server, NOT in any cluster.
  If the WebSphere App Server is part of a cluster, setting the
  enableHASupport to false may NOT give the desired results.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of WebSphere Application Server    *
  *                 V7.0.                                        *
  *                                                              *
  ****************************************************************
  * PROBLEM DESCRIPTION: Resource Adapter endpoints are not      *
  *                      activated on z/OS when the custom       *
  *                      property enableHASupport=true           *
  *                                                              *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The HA member state comparison to ACTIVATING always returns
  false in z/OS because we do a reference comparison (==) and not
  an object comparison (.equals). In z/OS this does not work as
  the HA manager runs in the control region while the comparison
  happens in the servant region where the application server
  runs. The HA member state is serialized and sent from the
  control process to the servant process and a reference
  comparison will always return false. This results in the code
  always considering the HA member as inactive and not activating
  the endpoint.
  

Problem conclusion

• The comparison of HA member state has been changed to an
  object comparison. This results in the objects being compared
  via the .equals() method.
  
  APAR PM08126 is currently targeted for inclusion in Service
  Level (Fix Pack) 7.0.0.9 of WebSphere Application Server V7.0.
  
  Please refer to URL:
  //www.ibm.com/support/docview.wss?rs=404&uid=swg27006970
  for Fix Pack availability.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

  PK93000

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

Modules/Macros

• BBGUBINF BBOUBINF
  

Fix information

• Fixed component name

  WEBSPHERE FOR Z

• Fixed component ID

  5655I3500

Applicable component levels

• R700 PSY UK55155

     UP10/03/26 P F003

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.