Large memory consumption when sending large web services requests
 Technote (FAQ)
 
Problem
The WebSphere® web services engine consumes an excessive amount of memory when processing messages.
 
Cause
In 6.0.2, the JVM™ may take up 12 times the SOAP message size when processing incoming messages. For example, if the SOAP message is 10MB large, you may see the heap size grow 120MB.

Prior to 6.0.2., the JVM may need up to 24 times the size of the SOAP message. For example, if the SOAP message is 10MB large, you may see the heap size grow 240MB.

The Java heap may look like the following:
*******************************************************************
234,087,544 [200] 22 {instance class} -                                  
org/apache/commons/discovery/tools/ManagedProperties$Value 0xdcaa9af0    
234,087,248 [216] 27 {instance class} -                                
com/ibm/ws/webservices/engine/events/P2DConverter$Scopes 0xdcaa9730      
 234,085,520 [272] 39 {instance class} -                                
com/ibm/ws/webservices/engine/encoding/DeserializationContextImpl        
0xdcaa3898                                                              
  234,079,832 [1,856] 294 {constant pool} 0xdcaa13f0                    
   214,513,160 [272] 41 {instance class} -                              
com/ibm/ws/webservices/engine/utils/XMLUtils 0xdca9d818                  
    214,504,560 [24] 2 java.util.Stack 0xb0f69d58                      
     214,504,536 [56] 6 [Ljava.lang.Object; 0xb0f7b590                  
      100,688,392 [24] 2 jaxp.SAXParserImpl 0xb0fb7780                  
      50,795,728 [24] 2 jaxp.SAXParserImpl 0xb151b9a8                  
      50,356,568 [24] 2 jaxp.SAXParserImpl 0xb1bc5a50                  
      12,607,832 [24] 2 jaxp.SAXParserImpl 0xb1bc5a68                  
      55,960 [24] 2 jaxp.SAXParserImpl 0xbea434a8                      
      192 [192] 14 {object array class} - [Ljava/lang/Object;          
0xdb0570c0                                                               *******************************************************************

 
Solution
This is a limitation. The recommended design pattern is to try to use the smallest SOAP messages possible. Alternatively, the JVM heap size can be increased.
 
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > Web Services (for example: SOAP or UDDI or WSGW or WSIF)
Operating system(s): Windows
Software version: 6.0
Software edition:
Reference #: 1221284
IBM Group: Software Group
Modified date: Oct 31, 2005