PI40869: OUT OF MEMORY WHEN TOO MANY WEBSERVICE-REF ELEMENTS IN EJB-JAR.X ML

8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21

APAR status

• Closed as program error.

Error description

• Too many webservice-ref elements in an ejb-jar.xml might cause
  an OutOfMemory error.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  IBM WebSphere Application Server V8.5 users *
  *                  of JAX-WS web services in an EJB module.    *
  ****************************************************************
  * PROBLEM DESCRIPTION: An OutOfMemory might occur when         *
  *                      there are many "service-ref"            *
  *                      elements in an ejb-jar.xml.             *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  A session bean could inject a webservice by "service-ref"
  elements in an ejb-jar.xml. Every service-ref will take some
  memory, but it will take a huge amount of memory if there are
  lots of session beans references to serveral webservices.
  Assume there are m session beans, and every session bean has n
  service-ref element, then it will need cache m*n service-ref
  elements. This will need a lot of memory.
  

Problem conclusion

• A new jvm custom property
  "com.ibm.webservice.OptimizeServiceRef" is added to the
  WebSphere Application Server to allow reuse of the cached
  "service-ref" elements. When the value is set to true, the
  cached "service-ref" information will be reused instead of
  creating a new one. When the property is set to false, this
  fix will not take affect. The default value of this property
  is false.
  
  The following Knowledge Center topic describes how to set
  a JVM property:
  
  http://www-
  01.ibm.com/support/knowledgecenter/SSEQTP_8.5.5//com.ibm.websphe
  re.base.iseries.doc/ae/trun_jvm.html
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.5.5.7.  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