Support Article

Out of memory errors on new EBank nodes



User has installed four new nodes. On these nodes, without any load on the system, the pulse stops running and out of memory errors occurred.

Error Messages

[9/18/16 19:54:00:134 EEST] 0000017e InSelectorImp W com.hazelcast.nio.InSelectorImpl [xx.xx.xx.xx]:5701 [93c8738d4ace9a38227c8262d256848c] [3.2] Selector exception at hz._hzInstance_1_93c8738d4ace9a38227c8262d256848c.IO.thread-in-1, cause= java.lang.OutOfMemoryError: Failed to create a thread: retVal -1073741830, errno 11
java.lang.OutOfMemoryError: Failed to create a thread: retVal -1073741830, errno 11


Steps to Reproduce

No specific steps.

Root Cause

A defect or configuration issue in the operating environment.

The four new nodes cannot communicate to other nodes to form the Elastic Search cluster because the firewall has not port opened (port 9300 to 9399) between new nodes and old nodes.
This results in an excessive number of thread being created.

This can be detected by looking at thread with name 
“PegaRULES-Search” in “Web Tiers Thread Management” in SMA. If user sees hundreds of them, this is not right.


Perform the following local-change:

On the firewall, open port used by Elastic Search (port 9300 to 9399).



Published September 27, 2016 - Updated October 6, 2016

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.