Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

After configuring a large amount of File Adapter sender channels, the J2EE Engine becomes very slow and some services start to block. How can I solve this issue?

April 26, 2017adapter channels configuring engine file j2ee large sender Services slow

0

Posted

After configuring a large amount of File Adapter sender channels, the J2EE Engine becomes very slow and some services start to block. How can I solve this issue?

1 Answer

0

Posted

Up to and including XI 3.0 SP13 each File Adapter sender channel permanently consumes a J2EE application thread. To solve this issue, increase the number of configured J2EE application threads using the SAP J2EE Engine Config Tool (“cluster-data” -> “Global server configuration” -> “managers” -> “ApplicationThreadManager” -> “MaxThreadCount”). Starting with XI 3.0 SP14 / PI 7.0 application threads are allocated on demand by the File Adapter and returned to the thread pool after it has finished the polling sequence, so thread shortage situations will typically occur much more rarely than with earlier SPs. 22.