[Solved] Issue with ignition, conection

Ignition
,
1

Hello everyone, I am having an issue with ignition , because I got an 503 error and is disconnected so many times and know says this :

java.lang.Exception: Error running query:
com.inductiveautomation.factorypmi.application.gateway.NQuery@3d2f7157@0ms
On: estadisticasCanales.Root Container.tblEsadisticasCaneles.data
at com.inductiveautomation.factorypmi.application.gateway.QueryManager$QueryExecutor.run(QueryManager.java:311)
at java.base/java.lang.Thread.run(Unknown Source)
Caused by: com.inductiveautomation.ignition.client.gateway_interface.GatewayException: Java heap space
at com.inductiveautomation.ignition.client.gateway_interface.GatewayInterface.newGatewayException(GatewayInterface.java:351)
at com.inductiveautomation.ignition.client.gateway_interface.GatewayInterface.sendMessage(GatewayInterface.java:325)
at com.inductiveautomation.ignition.client.gateway_interface.GatewayInterface.sendMessage(GatewayInterface.java:278)
at com.inductiveautomation.ignition.client.gateway_interface.GatewayInterface.invoke(GatewayInterface.java:945)
at com.inductiveautomation.ignition.designer.db.namedquery.DesignerNamedQueryManager.execute(DesignerNamedQueryManager.java:73)
at com.inductiveautomation.ignition.designer.db.namedquery.DesignerNamedQueryManager.execute(DesignerNamedQueryManager.java:46)
at com.inductiveautomation.factorypmi.application.gateway.NQuery.execute(NQuery.java:70)
at com.inductiveautomation.factorypmi.application.gateway.QueryManager$Query.execute(QueryManager.java:668)
at com.inductiveautomation.factorypmi.application.gateway.QueryManager$QueryExecutor.run(QueryManager.java:308)
… 1 more
Caused by: java.lang.OutOfMemoryError: Java heap space
at com.inductiveautomation.ignition.client.gateway_interface.ResponseParser.startElement(ResponseParser.java:361)
at java.xml/com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.startElement(Unknown Source)
at java.xml/com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanStartElement(Unknown Source)
at java.xml/com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(Unknown Source)
at java.xml/com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(Unknown Source)
at java.xml/com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at java.xml/com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown Source)
at java.xml/com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown Source)
at java.xml/com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(Unknown Source)
at java.xml/com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(Unknown Source)
at java.xml/com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
at com.inductiveautomation.ignition.client.gateway_interface.GatewayInterface.getResponse(GatewayInterface.java:485)
at com.inductiveautomation.ignition.client.gateway_interface.GatewayInterface.sendMessage(GatewayInterface.java:283)
… 8 more

Ignition v8.1.11 (b2021101912)
Java: Azul Systems, Inc. 11.0.11

2

Think this is the major issue here

1 Like
3

We edit the ignition.conf and we set the maxime memory as the manual says, but do not do the change in the gateway

4

Did you turn the gateway service off and on again? You must do this for ignition.conf changes to take effect.

5

yes, I did it and the ignition.conf still has the change but I can not see it in the gateway.
Stil has 2 gb in the maxime but I update it to 4 gb and still says 2 gb

6

That generally means you have multiple ignition.conf files (leftovers from prior installs, perhaps) and you edited the wrong one.

7

Oh yes, thank you, I edit the wrong one