Start of changeIBM FileNet P8, Version 5.2.1            

Asynchronous input/output native transport in WebSphere Application Server

In some cases, the asynchronous input/output native transport code can have a large native memory footprint. If the WebSphere® Application Server is limited on native memory, you can disable the asynchronous input/output native transport to increase the available address space for native memory.

You can disable asynchronous input/output native transport for WebSphere Application Server in the following environments:

There are two ways to disable the asynchronous input/output native transport code. You can either set the commClass WebContainer property or remove the native files. Setting the WebContainer is the easiest and safest method. If you remove or rename the asynchronous input/output libraries, these libraries might be reenabled the next time that you apply a WebSphere Application Server fix pack.



Last updated: March 2016
p8ppt326.htm

© Copyright IBM Corporation 2016.
End of change