0

I am getting a permgen space issue when trying to run an application. The application has a couple of select db calls and then tries to connect to salesforce system using the Salesforce connector. However, as soon I reach the point to connect to salesforce, I always get the following exception from the first deployment. Is there a way on cloudhub that I can do the profiling or debug the issue or give it more memory?BTW I am using one worker with 1.5GB of memory.

********************************************************************************
Message               : PermGen space (java.lang.OutOfMemoryError). Message payload is of type: LinkedHashMap
Code                  : MULE_ERROR-29999
--------------------------------------------------------------------------------
Exception stack is:
1. PermGen space (java.lang.OutOfMemoryError)
  java.lang.ClassLoader:-2 (null)
2. PermGen space (java.lang.OutOfMemoryError). Message payload is of type: LinkedHashMap (org.mule.api.MessagingException)
  org.mule.execution.ExceptionToMessagingExceptionExecutionInterceptor:32 (http://www.mulesoft.org/docs/site/current3/apidocs/org/mule/api/MessagingException.html)
--------------------------------------------------------------------------------
Root Exception stack trace:
java.lang.OutOfMemoryError: PermGen space
    at java.lang.ClassLoader.defineClass1(Native Method)
    at java.lang.ClassLoader.defineClass(ClassLoader.java:800)
    at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
    + 3 more (set debug level logging or '-Dmule.verbose.exceptions=true' for everything)
********************************************************************************
rst
  • 339
  • 5
  • 22

2 Answers2

2

If you're using a Mule 3.6.1 worker, this is a known issue that will be resolved soon. Unfortunately, Mule 3.6.1 CH workers have a low permgen setting. Could you try downgrading to Mule 3.6.0 and see whether the issue persists?

HTH,

Justin

justin.saliba
  • 724
  • 1
  • 9
  • 17
0

Increase the worker in cloudhub and try again. Example:If you were using 0.1 v core , try to increase to 0.2v core.

star
  • 1,493
  • 1
  • 28
  • 61
  • 1
    Switching to 3.6.0 does indeed appears to let this issue go away and from the thread dump, I can see the perm gen space max allocation was as low as around 90MB and hence was failing. – rst Apr 20 '15 at 10:13