PI94144: ORB CONNECTIONCACHEMIMIMUM CAN NOT BE SET TO 1 IN THE ADMIN-CONSOLE (10 IS THE CURRENT LIMIT)

9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
9.0.5.4: WebSphere Application Server traditional Version 9.0.5 Fix Pack 4
9.0.5.5: WebSphere Application Server traditional Version 9.0.5 Fix Pack 5
WebSphere Application Server traditional 9.0.5.6
9.0.5.7: WebSphere Application Server traditional Version 9.0.5 Fix Pack 7
9.0.5.8: WebSphere Application Server traditional Version 9.0.5.8
9.0.5.9: WebSphere Application Server traditional Version 9.0.5.9
9.0.5.10: WebSphere Application Server traditional Version 9.0.5.10
9.0.5.11: WebSphere Application Server traditional Version 9.0.5.11

APAR status

• Closed as program error.

Error description

• In the Integrated Solutions Console (admin-console) it is not
  possible to change the ORB Connection cache maximum settings to
  value "1". But for some application requirements it is needed to
  set this value to "1" to ensure that orb connection caching
  will be disabled.
  
  The iFix for this APAR will change this behaviour. Now the
  range of this property is between 1 through 2147483647.
  

Local fix

• You can change the connection cache maximum and minimum settings
  in the server.xml file:
  
  <services xmi:type="orb:ObjectRequestBroker"
  xmi:id="ObjectRequestBroker_1489683030253" enable="true"
  requestTimeout="180" requestRetriesCount="1"
  requestRetriesDelay="0"
  connectionCacheMaximum="240" connectionCacheMinimum="100" ...>
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server using the administrative console to  *
  *                  configure connection cache paramters.       *
  ****************************************************************
  * PROBLEM DESCRIPTION: The administrative console doesn't      *
  *                      allow the user to set the ORB           *
  *                      connection cache minimum to 1.          *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The validation for the ORB connection cache minimum is set to
  10.  Users want to set this value to 1.
  

Problem conclusion

• The validation.xml file was changed to allow customers to
  set
  the ORB connection cache minimum to one from the
  administrative console.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.5.5.14 and 9.0.0.8.
  Please refer to the Recommended Updates page for delivery
  information:
  http://www.ibm.com/support/docview.wss?
  rs=180&uid=swg27004980
  

Temporary fix

Comments

APAR Information

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

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

Fix information

• Fixed component name

  WEBS APP SERV N

• Fixed component ID

  5724H8800

Applicable component levels

• R850 PSY

     UP

• R900 PSY

     UP