Error description
The broker-wide HTTP Listener process retains large output buffers when processing large HTTP responses. This can eventually lead to OutOfMemory exceptions depending on the maximum JVM heap size configured for the HTTPListener, the size of the largest responses and the number of concurrent clients.
Local fix
Problem summary
**************************************************************** USERS AFFECTED: All users of WebSphere Message Broker V8.0 and IBM Integration Bus V9.0 who are using the broker-wide HTTP Listener. Platforms affected: z/OS, MultiPlatform **************************************************************** PROBLEM SUMMARY: The broker-wide HTTP Listener process sets the response buffer size to be equal to the size of the response message to prevent chunking. The tomcat server retains these large buffers and never re-sizes them down. This can eventually lead to java OutOfMemory exceptions depending on the maximum JVM heap size configured for the HTTPListener, the size of the largest responses and the number of concurrent clients. There are a number of resource name changes between WebSphere Message Broker and IBM Integration Bus Version 9.0. For details visit http://pic.dhe.ibm.com/infocenter/wmbhelp/v9r0m0/topic/com.ibm.e tools.mft.doc/bb23814_.htm
Problem conclusion
The broker-wide HTTPListener no longer sets the response buffer size to be the size of the response message. Instead an HTTP Content-Length header is explicitly added. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: Version Maintenance Level v8.0 8.0.0.5 v9.0 9.0.0.2 The latest available maintenance can be obtained from: http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041 If the maintenance level is not yet available, information on its planned availability can be found on: http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308 ---------------------------------------------------------------
No comments:
Post a Comment