In ConnectAll Java Heap size memory configurations setting to default values while upgrading from 2.11x to 3.x version
search cancel

In ConnectAll Java Heap size memory configurations setting to default values while upgrading from 2.11x to 3.x version

book

Article ID: 281676

calendar_today

Updated On:

Products

ConnectALL

Issue/Introduction

Steps to Reproduce: 

  • Navigate to $MULE_HOME/conf directory on an existing 2.11 instance
  • Open the wrapper.conf file and update the below values (default will be 1024 for both Initial and Maximum)

# Initial Java Heap Size (in MB)
wrapper.java.initmemory=1024

# Maximum Java Heap Size (in MB)
wrapper.java.maxmemory=4096 

  • Restart the mule services
  • Run the 3.3.0.2 installer to upgrade an existing 2.11 instance 
  • Post upgrade verify/validate the Java heap Size configurations available in below files

CONNECTALL_HOME/Core/bin/start-server.sh

CONNECTALL_HOME/Core/bin/connectall-core.xml

 

Expected Results: 

Java heap Size configurations availalbe in $MULE_HOME/conf/wrapper.conf file should migrate to below files

CONNECTALL_HOME/Core/bin/start-server.sh

CONNECTALL_HOME/Core/bin/connectall-core.xml

 

Actual Results:

Configurations overwritten to default i.e. 1024 in below files

CONNECTALL_HOME/Core/bin/start-server.sh

CONNECTALL_HOME/Core/bin/connectall-core.xml 

Environment

2.11.x

Cause

DE80248

Resolution

Workaround: 

Manually update the required java heap values in below files

CONNECTALL_HOME/Core/bin/start-server.sh

CONNECTALL_HOME/Core/bin/connectall-core.xml

Permanent fix will be provided in any upcoming release 

Additional Information

If Workaround not kept in place, so automation will be freeze and no record sync will happen OutOfMemoryError: Java heap space will come in mule logs and services restart required to unfreeze the automation sync