Heap growth from security providers stored in javax.crypto.SunJCE_b

Environment

• JBoss Enterprise Application Platform (EAP)

Issue

• We're getting OOMEs and the heap dump shows continued growth in the javax.crypto.SunJCE_b's "e" IdentityHashMap. This map contains many instances of a security provider we use.

Resolution

• Don't create a security provider repeatedly. Instead:
  • Instantiate the provider only once in the application.
  • Set up the provider in the $JAVA_HOME/jre/lib/security/java.security file

Root Cause

• Security provider created repeatedly

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.