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.
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.