Error loading project: java heap space


Since this morning, I can not access my ignition project. When I try to open it from the designer, I get this error :

Does anyone know how to fix this problem?

Thank you

If you are running on Windows try removing the cached files within .ignition or simply rename the folder. The designer will re-download all it needs on connecting to the Gateway again.

Which one should I remove?

Take a look under the C:\Users\your user\.ignition

Yes, thank you.
So I remove the “cache” folder here?

It contains this:

I tried it but it didn’t work.

If this is truly a Java Heap Error from the Designer side, open the Designer Launcher, and either under Settings (Global) or for the specific Gateway, modify the Max Heap setting. Likely your designer is set to 1024M (default). Increasing this to 2048M or something similar should get you beyond the issue.

If the issue is caused from the Gateway itself, then you might need to modify the ignition.conf file to adjust the parameter as well from the default 2048 (in MB) to something like 4096. You will have to restart the gateway afterwards for it to work. This can be validated by looking at the memory usage and see if it climbs anywhere near that 2048 MB mark ever.



The “full” details of the error would be useful to confirm, but from the error dialog it’s very likely the designer. Increasing the available memory in the launcher config is the way to go.

I’ll take a moment to soapbox - clearing the .ignition cache is very rarely the way to go.

hello, i got this problem today, i tried to delete the cache file and to increase the memory on the designer launcher from 1024 ti 2048, but it still not opening.
Here is the full error message below. I tried to open other projects on the same gateway and they are working well.

com.inductiveautomation.ignition.client.gateway_interface.GatewayException: Java heap space
	at com.inductiveautomation.ignition.client.gateway_interface.GatewayInterface.newGatewayException(
	at com.inductiveautomation.ignition.client.gateway_interface.GatewayInterface.sendMessage(
	at com.inductiveautomation.ignition.client.gateway_interface.GatewayInterface.sendMessage(
	at com.inductiveautomation.ignition.client.gateway_interface.GatewayInterface.invoke(
	at com.inductiveautomation.ignition.designer.gateway.DTGatewayInterface.loadProject(
	at com.inductiveautomation.ignition.designer.IgnitionDesigner$StartupProjectDialogHandler.lambda$new$2(
	at java.base/ Source)
Caused by: java.lang.OutOfMemoryError: Java heap space
	at com.inductiveautomation.ignition.client.gateway_interface.ResponseParser.startElement(
	at java.xml/ Source)
	at java.xml/ Source)
	at java.xml/$ Source)
	at java.xml/ Source)
	at java.xml/ Source)
	at java.xml/ Source)
	at java.xml/ Source)
	at java.xml/ Source)
	at java.xml/ Source)
	at java.xml/$JAXPSAXParser.parse(Unknown Source)
	at com.inductiveautomation.ignition.client.gateway_interface.GatewayInterface.getResponse(
	at com.inductiveautomation.ignition.client.gateway_interface.GatewayInterface.sendMessage(
	... 5 more

Ignition v8.1.15 (b2022030114)
Java: Azul Systems, Inc.

few days befor a warning about using more then 90% of the memory showed up in the gateway page.
and now :

Changing the designer allocation will not fix a problem with the gateway’s memory limit. That is set in ignition.conf, and a gateway restart is needed for it to take effect.

1 Like

where in the conf dir ?

The ${IGNITION_INSTALL_LOCATION}/data/ignition.conf file will have the memory settings here:

1 Like

Documentation: Gateway Configuration File Reference - Ignition User Manual 8.1 - Ignition Documentation

1 Like

thank you,
i have one more question about this, is it normal that the gateway use 900MB of memory even if non of the project is running or oppened, and it jumped to this just this week

update: it was my garbage collector. i did a reboot and now the memory usage droped to normal 200.

update2 : failed to allocate more memory, i changed maxmemory to 4096 (i have 8G in my debian machine) but on the gateway page it still marks 1024

I did restart the service, but it shows a "maybe failed to start message (the Gateway and the designer are working well)

Can you post your ignition.conf file so we can take a look?

# Configuration files must begin with a line specifying the encoding
#  of the the file.

# Wrapper License Properties (Ignored by Community Edition)
# Professional and Standard Editions of the Wrapper require a valid
#  License Key to start.  Licenses can be purchased or a trial license
#  requested on the following pages:

# Include file problems can be debugged by removing the first '#'
#  from the following line:

# The Wrapper will look for either of the following optional files for a
#  valid License Key.  License Key properties can optionally be included
#  directly in this configuration file.
#include ./wrapper-license.conf

# The following property will output information about which License Key(s)
#  are being found, and can aid in resolving any licensing problems.

# Wrapper Localization
# Specify the locale which the Wrapper should use.  By default the system
#  locale is used.
#wrapper.lang=en_US # en_US or ja_JP

# Specify the location of the Wrapper's language resources.  If these are
#  missing, the Wrapper will default to the en_US locale.

# Wrapper Java Properties
# Java Application
#  Locate the java binary on the system PATH:
#  Specify a specific java binary:

# Tell the Wrapper to log the full generated Java command line.

# Java Main class.  This class must implement the WrapperListener interface
#  or guarantee that the WrapperManager class is initialized.  Helper
#  classes are provided to do this for you.  See the Integration section
#  of the documentation for details.

# Java Classpath (include wrapper.jar)  Add class path elements as
#  needed starting from 1**

# Java Library Path (location of Wrapper.DLL or

# Java Bits.  On applicable platforms, tells the JVM to run in 32 or 64-bit mode.

# Java Additional Parameters,server=y,suspend=n,address=*:8000

# Initial Java Heap Size (in MB)

# Maximum Java Heap Size (in MB)

# Application parameters.  Add parameters as needed starting from 1


# Set this value to TRUE to allow ignition.conf to be reloaded when the JVM is restarted

# Wrapper Logging Properties
# Enables Debug output from the Wrapper.
# wrapper.debug=TRUE

# Format of output for the console.  (See docs for formats)

# Log Level for console output.  (See docs for log levels)

# Log file to use for wrapper output logging.

# Format of output for the log file.  (See docs for formats)

# Log Level for log file output.  (See docs for log levels)

# Maximum size that the log file will be allowed to grow to before
#  the log is rolled. Size is specified in bytes.  The default value
#  of 0, disables log rolling.  May abbreviate with the 'k' (kb) or
#  'm' (mb) suffix.  For example: 10m = 10 megabytes.

# Maximum number of rolled log files which will be allowed before old
#  files are deleted.  The default value of 0 implies no limit.

# Log Level for sys/event log output.  (See docs for log levels)

# Wrapper General Properties
# Allow for the use of non-contiguous numbered properties

# Title to use when running as a console
wrapper.console.title=Ignition Gateway

# Wrapper JVM Checks
# Detect DeadLocked Threads in the JVM. (Requires Standard Edition)

# Out Of Memory detection.
#wrapper.filter.message.1000=The JVM has run out of memory.


# Wrapper Email Notifications. (Requires Professional Edition)
# Common Event Email settings.<SMTP_Host>[%WRAPPER_HOSTNAME%:%WRAPPER_NAME%:%WRAPPER_EVENT_NAME%] Event Notification<Sender email><Recipient email>

# Configure the log attached to event emails.

# Enable specific event emails.

# Specify custom mail content JVM was restarted.\n\nPlease check on its status.\n

# Wrapper Windows NT/2000/XP Service Properties
# WARNING - Do not modify any of these properties when an application
#  using this configuration file has been installed as a service.
#  Please uninstall the service before modifying this section.  The
#  service can then be reinstalled.

# Name of the service

# Display name of the service
wrapper.displayname=Ignition Gateway

# Description of the service
wrapper.description=Ignition Gateway

# Service dependencies.  Add dependencies as needed starting from 1

# Mode in which the service is installed.  AUTO_START, DELAY_START or DEMAND_START

# Allow the service to interact with the desktop.


you Max memory is set to 2048 here…

So something isn’t quite right if you think you set it to 4096.

i thought that 4096 was too much, so I reduced it to 2048.

And you have restarted Ignition using gwcmd --restart and it still isn’t showing the updated memory?

yes , but the memory on the gateway stay the same