Troubleshooting
Delphix Masking / Delphix Masking Engine Admin Guide / Troubleshooting

Memory Usage

The Delphix Masking Engine masking operations can be memory- and processor-intensive. Therefore, the number of jobs that can run in parallel and the speed with which they run varies depending on processor and RAM.

Initially, we recommend that you allocate at least 1 GB for the Tomcat application server instance. Other application servers might require more memory; follow the suggested guidelines for your server. If you encounter memory issues, you might need to increase your memory allocation.

  • 32-bit Java Virtual Machines (JVMs) have a maximum memory setting (1.5 GB) that you cannot exceed. 64-bit JVMs do not have this restriction.

If you do not allocate enough memory initially, you could have issues if you try to allocate memory as needed. To avoid this problem, we suggest that you set your Java Xms and Xmx values to the same number. This ensures that all necessary memory is reserved and available for the job at the beginning. Otherwise, your operating system might attempt to terminate some lower priority processes to free up memory, which could halt your higher priority processes. We recommend allocating 1 GB per job.

For information on system requirements, see Delphix Masking Engine System Requirements.

Stack Traces

If an unhandled exception occurs in code, you might get a stack trace. If this happens, do the following:

  1. Restart the server.
  2. Ensure that the database is up.
  3. If the problem persists, contact Customer Support.

Application Server Down

If the application server is down, the application is also down. The repository might still be available, if the database server is still up. If the server is down, do the following:

  1. If necessary, restart the database server.
  2. Restart the application server.
  3. Ensure that both servers are up and running.
  4. If the problem persists, contact Customer Support.

Database Server Down

If the database server is down, do the following:

  1. Restart the database server.
  2. If necessary, restart the application server.
  3. Ensure that both servers are up and running.
  4. If the problem persists, contact Customer Support.

Related Links