IBM App Connect Enterprise, Version 11.0.0.2
Operating Systems: Windows, Linux
You experience configuration problems with multiple components
Follow this guidance to resolve configuration problems with multiple components.
Procedure
Scenario: You are experiencing configuration problems with many components.
Explanation: If you are running IBM® App Connect
Enterprise with many configured components, the memory footprint of the integration node processes (particularly the integration servers or DataFlowEngines) might exceed their memory limits. In particular, the user process limit might be exceeded, or the address space limit might be reached. You might encounter problems, such as the BIP2106E or BIP2137E error messages, when running an integration node with:
Many message flows
Multiple databases
Large input or output messages
Solution: Use tools that are specific to your operating system to check the maximum size of the failing process, then check for any user limits (if applicable) or computer limits on process size.
On Windows, the maximum process size is 2 GB. Increasing user limits beyond this value does not make any difference. If your integration node processes regularly reach this size, consider spreading your message flows across more integration servers to reduce the size of each one below these limits.
On HP-UX, the number of threads per process is limited by the kernel parameter max_thread_proc. The more flows you add to an integration server, the more threads you use for each process. If you need many flows in an integration server, increase the value of the max_thread_proc kernel parameter. Try setting the kernel parameter max_thread_proc to 256, or to 512 if you are using WebSphere® Transformation Extender (WTX).