The issue addressed in this article is resolved for new installations of vCommander 6.0 or later, but upgrading customers will need to make the change manually. Unless you are experiencing performance issues or have been directed to make this change by Embotics Technical Support, there is no pressing need to carry out this procedure outside of your next scheduled maintenance window.


The procedure below updates the size of your Java Max Permanent space, to avoid out of memory errors which could otherwise be thrown and to optimize performance. Log files will indicate there is a problem with errors that contain the string java.lang.OutOfMemoryError: PermGen space.


To configure MaxPermSize Size, follow the procedure below.

  1.   Login to Windows on the vCommander application server.
  2.   In Windows Explorer, browse to \<Install_Dir>\Embotics\vCommander\tomcat\bin\.
  3.   Right-click vlmw.exe and choose to Run as Administrator.
  4.   Switch to the Java tab.

    1Ma2d-OtYfjVpdBR3t51GyKcDdojB4xv7A.png

  5. Edit -XX:MaxPermSize=320m to read -XX:MaxPermSize=400m.
  6. Click Apply and OK.
  7. Restart the vCommander Windows Service.