MuleSoft

Introduction How to over come "org.apache.xml.security.encryption.XMLEncryptionException: Illegal key size or default parameters" or "java.security.InvalidKeyException:illegal Key Size" error when invoking secured services These "org.apache.xml.security.encryption.XMLEncryptionException: Illegal key size or default parameters" or "java.security.InvalidKeyException:illegal Key Size" error usually occurs when we try to invoke a web services in a secured manner and your JVM is not provisioned for Java unlimited security jurisdiction. To provision for the Java unlimited security jurisdiction we have to install Java Cryptography Extension (JCE) unlimited strength jurisdiction policy files. How to Install JCE Windows - Go to the Oracle Java SE download page Scroll down ... Under "Additional Resources" section you will find "Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy File" Download the

Introduction This article provides the solution/prevention to the API’s OutOfMemory error where operating system is unable to create new native thread. The operating system is limiting the number of threads your Mule process can spawn, or the memory settings are wrong (setting more memory than the physically available memory). Memory Calculation The usage of memory in Java is determined by the following formula:  Max memory = [-Xmx] + [-XX:MaxPermSize] + number_of_threads * [-Xss]  Most of the time the focus is in the Heap size determined by the JVM argument -Xmx and eventually, in Oracle JVMs, the Permanent Generation Space, specified by the argument -XX:MaxPermSize. However you must also consider how many threads will your Mule instance handle, as it also adds to the max memory usage. For Example Suppose you have the following parameters:  Max Heap size: 3072 MB  Max PermGen size: 512 MB If your system has in total 4GB RAM, then you would think that the 512 MB lef