Resolution:
Description:
===========
A memory leak was observed when using the HTTP Channel. Even after applying the TIBCO BusinessEvents 5.1.1 hotfix03, the engine still fails at startup.

Environment:
===========
TIBCO BusinessEvents 5.1.1 Hotfix3
All Operating Systems


Symptoms:
=========
As described in the BE 5.1.1 HF3 readme:

*************************
BE-18620
A memory leak was observed when using the HTTP Channel. To enable the fix,
update the garbage collection parameter in be-engine.tra as follows:

java.extended.properties=-server -Xms2048m -Xmx2048m -XX:NewSize=1228M
-javaagent:%BE_HOME%/lib/cep-base.jar -XX:MaxPermSize=512m -XX:+UseParNewGC -XX:+UseConcMarkSweepGC

Note: The new parameter for garbage collection must be set to 60% of the available heap. For example, if the available heap size is 2048M, the garbage collection parameter 'NewSize' is set to 1228M.
*************************

When using the property like:

java.extended.properties=-server –Xms1024m –Xmx1024m -XX:NewSize=614M -javaagent:%BE_HOME%/lib/cep-base.jar -XX:MaxPermSize=256m -XX:+UseParNewGC -XX:+UseConcMarkSweepGC

The engine fails at start up and the following error is thrown:

"Too small initial heap for the new size specified."


Cause:
======
MaxPermSize identifies the max size of perm space which holds JVM structures and class objects. It may be possible that the JVM fails to start if the perm space is too small.

Resolution:
========
Increase the MaxPermSize by modifying the property to:

java.extended.properties=-server –Xms1024m –Xmx1024m -XX:NewSize=614M -javaagent:%BE_HOME%/lib/cep-base.jar -XX:MaxPermSize=512m -XX:+UseParNewGC -XX:+UseConcMarkSweepGC

Memory leak was observed when using the HTTP Channel. Engine fails at startup after applying hotfix.